Query-specific behavioral modification of tree traversal

ABSTRACT

Methods and systems are described in some examples for changing the traversal of an acceleration data structure in a highly dynamic query-specific manner, with each query specifying test parameters, a test opcode and a mapping of test results to actions. In an example ray tracing implementation, traversal of a bounding volume hierarchy by a ray is performed with the default behavior of the traversal being changed in accordance with results of a test performed using the test opcode and test parameters specified in the ray data structure and another test parameter specified in a node of the bounding volume hierarchy. In an example implementation a traversal coprocessor is configured to perform the traversal of the bounding volume hierarchy.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to the following commonly-assigned USpatents and patent applications, the entire contents of each of whichare incorporated by reference: U.S. application Ser. No. 14/563,872titled “Short Stack Traversal of Tree Data Structures” filed Dec. 8,2014; U.S. Pat. No. 9,582,607 titled “Block-Based Bounding VolumeHierarchy”; U.S. Pat. No. 9,552,664 titled “Relative Encoding For ABlock-Based Bounding Volume Hierarchy” as; U.S. Pat. No. 9,569,559titled “Beam Tracing” filed Mar. 18, 2015; U.S. Pat. No. 10,025,879titled “Tree Data Structures Based on a Plurality of Local CoordinateSystems”; U.S. application Ser. No. 14/737,343 titled “Block-BasedLossless Compression of Geometric Data” filed Jun. 11, 2015; and thefollowing U.S. Applications filed concurrently herewith:

-   -   (Atty. Docket: 6610-0032/18-AU-0127) titled “Method for        Continued Bounding Volume Hierarchy Traversal On Intersection        Without Shader Intervention”;    -   (Atty. Docket: 6610-0033/18-AU-0128) titled “Method for        Efficient Grouping of Cache Requests for Datapath Scheduling”;    -   (Atty. Docket: 6610-0034/18-SC-0144) titled “Robust, Efficient        Multiprocessor-Coprocessor Interface”;    -   (Atty. Docket 6610-0036/18-SC-0145) titled “Conservative        Watertight Ray Triangle Intersection”;    -   (Atty. Docket 6610-0037/18-SC-0149) titled “Method for Handling        Out-of-Order Opaque and Alpha Ray/Primitive Intersections”; and    -   (Atty. Docket 6610-0039/18-AU-0170) titled “Method for Forward        Progress and Programmable Timeouts of Tree Traversal Mechanisms        in Hardware”.

FIELD

The present technology relates to computer graphics, and moreparticularly to ray tracers. More particularly, the technology relatesto hardware acceleration of computer graphics processing including butnot limited to ray tracing. Still more particularly, the examplenon-limiting technology herein relates to a hardware-based traversalcoprocessor that efficiently traverses an acceleration data structuree.g., for real time ray tracing and query-specific modification of thecoprocessor's traversal behavior.

BACKGROUND & SUMMARY

If you look around the visual scene before you, you will notice thatsome of the most interesting visual effects you see are produced bylight rays interacting with surfaces. This is because light is the onlything we see. We don't see objects—we see the light that is reflected orrefracted by the objects. Most of the objects we can see reflect light(the color of an object is determined by which parts of light the objectreflects and which parts it absorbs). Shiny surfaces such as metallicsurfaces, glossy surfaces, ceramics, the surfaces of liquids and avariety of others (even the corneas of the human eyes) act as mirrorsthat specularly reflect light. For example, a shiny metal surface willreflect light at the same angle as it hit the surface. An object canalso cast shadows by preventing light from reaching other surfaces thatare behind the object relative to a light source. If you look around,you will notice that the number and kinds of reflections and the number,kinds and lengths of shadows depend on many factors including the numberand type of lights in the scene. A single point light such as a singlefaraway light bulb will produce single reflections and hard shadows.Area light sources such as windows or light panels produce differentkinds of reflection highlights and softer shadows. Multiple lights willtypically produce multiple reflections and more complex shadows (forexample, three separated point light sources will produce three shadowswhich may overlap depending on the positions of the lights relative toan object).

If you move your head as you survey the scene, you will notice that thereflections change in position and shape (the shadows do the same). Bychanging your viewpoint, you are changing the various angles of thelight rays your eyes detect. This occurs instantaneously—you move yourhead and the visual scene changes immediately.

The simple act of drinking a cup of tea is a complex visual experience.The various shiny surfaces of the glossy ceramic cup on the table beforeyou reflect each light in the room, and the cup casts a shadow for eachlight. The moving surface of the tea in the cup is itself reflective.You can see small reflected images of the lights on the tea's surface,and even smaller reflections on the part of the tea's surface where theliquid curves up to meet the walls of the cup. The cup walls also castshadows onto the surface of the liquid in the cup. Lifting the cup toyour mouth causes these reflections and shadows to shift and shimmer asyour viewpoint changes and as the surface of the liquid is agitated bymovement.

We take these complexities of reflections and shadows for granted. Ourbrains are adept at decoding the positions, sizes and shapes of shadowsand reflections and using them as visual cues. This is in part how wediscern the position of objects relative to one another, how wedistinguish one object from another and how we learn what objects aremade of Different object surfaces reflect differently. Specular (mirrortype) reflection of hard metal creates images of reflected objects,while diffuse reflection off of rough surfaces is responsible for colorand lights up objects in a softer way. Shadows can be soft and diffuseor hard and distinct depending on the type of lighting, and the lengthsand directions of the shadows will depend on the angle of the light raysrelative to the object and our eyes.

Beginning artists typically don't try to show reflection or shadows.They tend to draw flat scenes that have no shadows and no reflections orhighlights. The same was true with computer graphics of the past.

Real time computer graphics have advanced tremendously over the last 30years. With the development in the 1980's of powerful graphicsprocessing units (GPUs) providing 3D hardware graphics pipelines, itbecame possible to produce 3D graphical displays based on texture-mappedpolygon primitives in real time response to user input. Such real timegraphics processors were built upon a technology called scan conversionrasterization, which is a means of determining visibility from a singlepoint or perspective. Using this approach, three-dimensional objects aremodeled from surfaces constructed of geometric primitives, typicallypolygons such as triangles. The scan conversion process establishes andprojects primitive polygon vertices onto a view plane and fills in thepoints inside the edges of the primitives. See e.g., Foley, Van Dam,Hughes et al, Computer Graphics: Principles and Practice (2d Ed.Addison-Wesley 1995 & 3d Ed. Addison-Wesley 2014).

Hardware has long been used to determine how each polygon surface shouldbe shaded and texture-mapped and to rasterize the shaded, texture-mappedpolygon surfaces for display. Typical three-dimensional scenes are oftenconstructed from millions of polygons. Fast modern GPU hardware canefficiently process many millions of graphics primitives for eachdisplay frame (every 1/30^(th) or 1/60^(th) of a second) in real timeresponse to user input. The resulting graphical displays have been usedin a variety of real time graphical user interfaces including but notlimited to augmented reality, virtual reality, video games and medicalimaging. But traditionally, such interactive graphics hardware has notbeen able to accurately model and portray reflections and shadows.

Some have built other technologies onto this basic scan conversionrasterization approach to allow real time graphics systems to accomplisha certain amount of realism in rendering shadows and reflections. Forexample, texture mapping has sometimes been used to simulate reflectionsand shadows in a 3D scene. One way this is commonly done is totransform, project and rasterize objects from different perspectives,write the rasterized results into texture maps, and sample the texturemaps to provide reflection mapping, environment mapping and shadowing.While these techniques have proven to be useful and moderatelysuccessful, they do not work well in all situations. For example,so-called “environment mapping” may often require assuming theenvironment is infinitely distant from the object. In addition, anenvironment-mapped object may typically be unable to reflect itself Seee.g.,http://developer.download.nvidia.com/CgTutorial/cg_tutorial_chapter07.html.These limitations result because conventional computer graphicshardware—while sufficiently fast for excellent polygon rendering—doesnot perform the light visualization needed for accurate and realisticreflections and shadows. Some have likened raster/texture approximationsof reflections and shadows as the visual equivalent of AM radio.

There is another graphics technology which does perform physicallyrealistic visibility determinations for reflection and shadowing. It iscalled “ray tracing”. Ray tracing was developed at the end of the 1960'sand was improved upon in the 1980's. See e.g., Apple, “Some Techniquesfor Shading Machine Renderings of Solids” (SJCC 1968) pp. 27-45;Whitted, “An Improved Illumination Model for Shaded Display” Pages343-349 Communications of the ACM Volume 23 Issue 6 (June 1980); andKajiya, “The Rendering Equation”, Computer Graphics (SIGGRAPH 1986Proceedings, Vol. 20, pp. 143-150). Since then, ray tracing has beenused in non-real time graphics applications such as design and filmmaking. Anyone who has seen “Finding Dory” (2016) or other Pixaranimated films has seen the result of the ray tracing approach tocomputer graphics—namely realistic shadows and reflections. See e.g.,Hery et al, “Towards Bidirectional Path Tracing at Pixar” (2016).

Ray tracing is a primitive used in a variety of rendering algorithmsincluding for example path tracing and Metropolis light transport. In anexample algorithm, ray tracing simulates the physics of light bymodeling light transport through the scene to compute all global effects(including for example reflections from shiny surfaces) using rayoptics. In such uses of ray tracing, an attempt may be made to traceeach of many hundreds or thousands of light rays as they travel throughthe three-dimensional scene from potentially multiple light sources tothe viewpoint. Often, such rays are traced relative to the eye throughthe scene and tested against a database of all geometry in the scene.The rays can be traced forward from lights to the eye, or backwards fromthe eye to the lights, or they can be traced to see if paths startingfrom the virtual camera and starting at the eye have a clear line ofsight. The testing determines either the nearest intersection (in orderto determine what is visible from the eye) or traces rays from thesurface of an object toward a light source to determine if there isanything intervening that would block the transmission of light to thatpoint in space. Because the rays are similar to the rays of light inreality, they make available a number of realistic effects that are notpossible using the raster based real time 3D graphics technology thathas been implemented over the last thirty years. Because eachilluminating ray from each light source within the scene is evaluated asit passes through each object in the scene, the resulting images canappear as if they were photographed in reality. Accordingly, these raytracing methods have long been used in professional graphicsapplications such as design and film, where they have come to dominateover raster-based rendering.

The main challenge with ray tracing has generally been speed. Raytracing requires the graphics system to compute and analyze, for eachframe, each of many millions of light rays impinging on (and potentiallyreflected by) each surface making up the scene. In the past, thisenormous amount of computation complexity was impossible to perform inreal time.

One reason modern GPU 3D graphics pipelines are so fast at renderingshaded, texture-mapped surfaces is that they use coherence efficiently.In conventional scan conversion, everything is assumed to be viewedthrough a common window in a common image plane and projected down to asingle vantage point. Each triangle or other primitive is sent throughthe graphics pipeline and covers some number of pixels. All relatedcomputations can be shared for all pixels rendered from that triangle.Rectangular tiles of pixels corresponding to coherent lines of sightpassing through the window may thus correspond to groups of threadsrunning in lock-step in the same streaming processor. All the pixelsfalling between the edges of the triangle are assumed to be the samematerial running the same shader and fetching adjacent groups of texelsfrom the same textures. In ray tracing, in contrast, rays may start orend at a common point (a light source, or a virtual camera lens) but asthey propagate through the scene and interact with different materials,they quickly diverge. For example, each ray performs a search to findthe closest object. Some caching and sharing of results can beperformed, but because each ray potentially can hit different objects,the kind of coherence that GPU's have traditionally taken advantage ofin connection with texture mapped, shaded triangles is not present(e.g., a common vantage point, window and image plane are not there forray tracing). This makes ray tracing much more computationallychallenging than other graphics approaches—and therefore much moredifficult to perform on an interactive basis.

Much research has been done on making the process of tracing rays moreefficient and timely. See e.g., Glassner, An Introduction to Ray Tracing(Academic Press Inc., 1989). Because each ray in ray tracing is, by itsnature, evaluated independently from the rest, ray tracing has beencalled “embarrassingly parallel.” See e.g., Akenine-Möller et al., RealTime Rendering at Section 9.8.2, page 412 (Third Ed. CRC Press 2008). Asdiscussed above, ray tracing involves effectively testing each rayagainst all objects and surfaces in the scene. An optimization called“acceleration data structure” and associated processes allows thegraphics system to use a “divide-and-conquer” approach across theacceleration data structure to establish what surfaces the ray hits andwhat surfaces the ray does not hit. Each ray traverses the accelerationdata structure in an individualistic way. This means that dedicatingmore processors to ray tracing gives a nearly linear performanceincrease. With increasing parallelism of graphics processing systems,some began envisioning the possibility that ray tracing could beperformed in real time. For example, work at Saarland University in themid-2000's produced an early special purpose hardware system forinteractive ray tracing that provided some degree of programmability forusing geometry, vertex and lighting shaders. See Woop et al., “RPU: AProgrammable Ray Processing Unit for Real Time Ray Tracing” (ACM 2005).As another example, Advanced Rendering Technology developed“RenderDrive” based on an array of AR250/350 rendering processorsderived from ARM1 and enhanced with custom pipelines for ray/triangleintersection and SIMD vector and texture math but with no fixed-functiontraversal logic. See e.g.,http://www.graphicshardware.org/previous/www_2001/presentations/Hot3D_Daniel_Hall.pdf

Then, in 2010, NVIDIA took advantage of the high degree of parallelismof NVIDIA GPUs and other highly parallel architectures to develop theOptiX™ ray tracing engine. See Parker et al., “OptiX: A General PurposeRay Tracing Engine” (ACM Transactions on Graphics, Vol. 29, No. 4,Article 66, July 2010). In addition to improvements in API's(application programming interfaces), one of the advances provided byOptiX™ was improving the acceleration data structures used for findingan intersection between a ray and the scene geometry. Such accelerationdata structures are usually spatial or object hierarchies used by theray tracing traversal algorithm to efficiently search for primitivesthat potentially intersect a given ray. OptiX™ provides a number ofdifferent acceleration structure types that the application can choosefrom. Each acceleration structure in the node graph can be a differenttype, allowing combinations of high-quality static structures withdynamically updated ones.

The OptiX™ programmable ray tracing pipeline provided significantadvances, but was still generally unable by itself to provide real timeinteractive response to user input on relatively inexpensive computingplatforms for complex 3D scenes. Since then, NVIDIA has been developinghardware acceleration capabilities for ray tracing. See e.g., U.S. Pat.Nos. 9,582,607; 9,569,559; US 20160070820; and US 20160070767.

Given the great potential of a truly interactive real time ray tracinggraphics processing system for rendering high quality images ofarbitrary complexity in response for example to user input, further workis possible and desirable.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example non-limiting ray tracing graphics system.

FIG. 2A shows an example specular object.

FIG. 2B shows the example object within a bounding volume.

FIG. 2C shows an example volumetric subdividing of the FIG. 2B boundingvolume.

FIGS. 2D, 2E and 2F show example further levels of volumetricsubdivision of the bounding volume to create a bounding volume hierarchy(BVH).

FIG. 2G shows an example portion of the object comprised of primitivesurfaces, in this case triangles.

FIGS. 3A-3C show example simplified ray tracing tests to determinewhether the ray passes through a bounding volume containing geometry andwhether the ray intersects geometry.

FIG. 4 illustrates an example ray tracing flowchart.

FIGS. 5A-5C show example different ray-primitive intersection scenarios.

FIGS. 6A and 6B show an example of how texture mapping can impactray-primitive intersection results.

FIGS. 7A and 7B illustrate ray instance transforms.

FIG. 8A illustrates an example non-limiting bounding volume hierarchy(BVH).

FIG. 8B shows an example acceleration data structure in the form of agraph or tree.

FIG. 9 shows a simplified example non-limiting traversal co-processorcomprising a tree traversal unit (TTU).

FIG. 10A illustrates an example non-limiting ray tracing shadingpipeline flowchart.

FIGS. 10B and 10C illustrate more detailed ray tracing pipelines.

FIG. 11A illustrates an example query data structure, according to someembodiments.

FIG. 11B shows an example node data structure in the BVH, according tosome embodiments.

FIG. 12 illustrates an example traversal stack data structure, accordingto some embodiments.

FIG. 13 shows an example result queue data structure, according to someembodiments.

FIG. 14 illustrates a process showing the auxiliary ray operation testbeing performed for bounding volumes in the BVH during traversal,according to some embodiments.

FIG. 15 illustrates a process showing the process of FIG. 14 when a leafnode is intersected, according to some example embodiments.

FIG. 16 illustrates a process showing the process of FIG. 14 when theray operation test result is passed to the ray-primitive testing block,according to some example embodiments.

FIG. 17 illustrates an example parallel processing unit (PPU).

FIG. 18 illustrates an example memory partition unit.

FIG. 19 illustrates an example general processing cluster (GPC) withinthe parallel processing unit of FIG. 17.

FIGS. 20 and 21 illustrate an example streaming multi-processor.

FIG. 22 is a conceptual diagram of a processing system implemented usingPPUs of FIG. 17.

FIG. 23 expands FIG. 22 to show additional interconnected devices.

FIG. 24 is a conceptual diagram of a graphics processing pipelineimplemented by the GPC of FIG. 19.

DETAILED DESCRIPTION OF NON-LIMITING EMBODIMENTS

The technology herein provides hardware capabilities that accelerate raytracing to such an extent that it brings the power of ray tracing togames and other interactive real time computer graphics, initiallyenabling high effect quality in shadows and reflections and ultimatelyglobal illumination. In practice, this means accelerating ray tracing bya factor of up to an order of magnitude or more over what would bepossible in software on the same graphics rendering system.

In more detail, the example non-limiting technology provides dedicatedhardware to accelerate ray tracing. In non-limiting embodiments, ahardware co-processor (herein referred to as a “traversal coprocessor”or in some embodiments a “tree traversal unit” or “TTU”) acceleratescertain processes supporting interactive ray tracing includingray-bounding volume intersection tests, ray-primitive intersection testsand ray “instance” transforms.

In some non-limiting embodiments, the traversal co-processor performsqueries on an acceleration data structure for processes running onpotentially massively-parallel streaming multiprocessors (SMs). Thetraversal co-processor traverses the acceleration data structure todiscover information about how a given ray interacts with an object theacceleration data structure describes or represents. For ray tracing,the traversal coprocessors are callable as opposed to e.g., fixedfunction units that perform an operation once between logical pipelinestages running different types of threads (e.g., vertex threads andpixel threads).

In some non-limiting embodiments, the acceleration data structurecomprises a hierarchy of bounding volumes (bounding volume hierarchy orBVH) that recursively encapsulates smaller and smaller bounding volumesubdivisions. The largest volumetric bounding volume may be termed a“root node.” The smallest subdivisions of such hierarchy of boundingvolumes (“leaf nodes”) contain items. The items could be primitives(e.g., polygons such as triangles) that define surfaces of the object.Or, an item could be a sphere that contains a whole new level of theworld that exists as an item because it has not been added to the BVH(think of the collar charm on the cat from “Men in Black” whichcontained an entire miniature galaxy inside of it). If the itemcomprises primitives, the traversal co-processor tests rays against theprimitives to determine which object surfaces the rays intersect andwhich object surfaces are visible along the ray.

The traversal co-processor performs a test of each ray against a widerange of bounding volumes, and can cull any bounding volumes that don'tintersect with that ray. Starting at a root node that bounds everythingin the scene, the traversal co-processor tests each ray against smaller(potentially overlapping) child bounding volumes which in turn bound thedescendent branches of the BVH. The ray follows the child pointers forthe bounding volumes the ray hits to other nodes until the leaves orterminal nodes (volumes) of the BVH are reached. Once the traversalco-processor traverses the acceleration data structure to reach aterminal or “leaf” node that contains a geometric primitive, it performsan accelerated ray-primitive intersection test that determines whetherthe ray intersects that primitive (and thus the object surface thatprimitive defines). The ray-primitive test can provide additionalinformation about primitives the ray intersects that can be used todetermine the material properties of the surface required for shadingand visualization. Recursive traversal through the acceleration datastructure enables the traversal co-processor to discover all objectprimitives the ray intersects, or the closest (from the perspective ofthe viewpoint) primitive the ray intersects (which in some cases is theonly primitive that is visible from the viewpoint along the ray).

The traversal co-processor also accelerates the transform of each rayfrom world space into object space to obtain finer and finer boundingbox encapsulations of the primitives and reduce the duplication of thoseprimitives across the scene. Objects replicated many times in the sceneat different positions, orientations and scales can be represented inthe scene as instance nodes which associate a bounding box and leaf nodein the world space BVH with a transformation that can be applied to theworld-space ray to transform it into an object coordinate space, and apointer to an object-space BVH. This avoids replicating the object spaceBVH data multiple times in world space, saving memory and associatedmemory accesses. The instance transform increases efficiency bytransforming the ray into object space instead of requiring the geometryor the bounding volume hierarchy to be transformed into world (ray)space and is also compatible with additional, conventional rasterizationprocesses that graphics processing performs to visualize the primitives.

Certain presently disclosed non-limiting embodiments thus provide atraversal co-processor, a new subunit of one or a group of streamingmultiprocessor SMs of a 3D graphics processing pipeline. In order tounderstand where the traversal co-processor fits in the overall picture,it may be helpful to understand a few fundamentals of the algorithmemployed by most or all modern ray tracers. But it should be pointed outthat the technology herein provides a generic capability to determine,for a thread running in a GPU, what the nearest visible thing is from agiven point along a specified direction, or if anything lies between twopoints. A common use case for such capability will be in processes thatstart tracing rays from points that have already been rasterized ontriangles using conventional scan conversion techniques. The disclosedtechnology can but does not necessarily replace or substitute for scanconversion technology, and may often augment it and be used inconjunction with scan conversion techniques to enhance images withphotorealistic reflections, shadows and other effects.

Ray Tracing Techniques

Generally, ray tracing is a rendering method in which rays are used todetermine the visibility of various elements in the scene. Ray tracingcan be used to determine if anything is visible along a ray (forexample, testing for occluders between a shaded point on a geometricprimitive and a point on a light source) and can also be used toevaluate reflections (which may for example involve performing atraversal to determine the nearest visible surface along a line of sightso that software running on a streaming processor can evaluate amaterial shading function corresponding to what was hit—which in turncan launch one or more additional rays into the scene according to thematerial properties of the object that was intersected) to determine thelight returning along the ray back toward the eye. In classicalWhitted-style ray tracing, rays are shot from the viewpoint through thepixel grid into the scene, but other path traversals are possible.Typically, for each ray, the closest object is found. This intersectionpoint can then be determined to be illuminated or in shadow by shootinga ray from it to each light source in the scene and finding if anyobjects are in between. Opaque objects block the light, whereastransparent objects attenuate it. Other rays can be spawned from anintersection point. For example, if the intersecting surface is shiny orspecular, rays are generated in the reflection direction. The ray mayaccept the color of the first object intersected, which in turn has itsintersection point tested for shadows. This reflection process isrecursively repeated until a recursion limit is reached or the potentialcontribution of subsequent bounces falls below a threshold. Rays canalso be generated in the direction of refraction for transparent solidobjects, and again recursively evaluated. See Akenine-Möller et al.,cited above. Ray tracing technology thus allows a graphics system todevelop physically correct reflections and shadows that are not subjectto the limitations and artifacts of scan conversion techniques.

Traversal Coprocessor

The basic task the traversal coprocessor performs is to test a rayagainst all primitives (commonly triangles in one embodiment) in thescene and report either the closest hit (according to distance measuredalong the ray) or simply the first (not necessarily closest) hitencountered, depending upon use case. The naïve algorithm would be anO(n) brute-force search. By pre-processing the scene geometry andbuilding a suitable acceleration data structure in advance, however, itis possible to reduce the average-case complexity to O(log n). In raytracing, the time for finding the closest (or for shadows, any)intersection for a ray is typically order O(log n) for n objects when anacceleration data structure is used. For example, bounding volumehierarchies (BVHs) of the type commonly used for modern ray tracingacceleration data structures typically have an O(log n) search behavior.

Bounding Volume Hierarchies

The acceleration data structure most commonly used by modern ray tracersis a bounding volume hierarchy (BVH) comprising nested axis-alignedbounding boxes (AABBs). The leaf nodes of the BVH contain the primitives(e.g., triangles) to be tested for intersection. The BVH is most oftenrepresented by a graph or tree structure data representation. In suchinstances, the traversal coprocessor may be called a “tree traversalunit” or “TTU”.

Given a BVH, ray tracing amounts to a tree search where each node in thetree visited by the ray has a bounding volume for each descendent branchor leaf, and the ray only visits the descendent branches or leaves whosecorresponding bound volume it intersects. In this way, only a smallnumber of primitives must be explicitly tested for intersection, namelythose that reside in leaf nodes intersected by the ray. In the examplenon-limiting embodiments, the traversal coprocessor accelerates bothtree traversal (including the ray-volume tests) and ray-primitive tests.As part of traversal, the traversal coprocessor can also handle“instance transforms”—transforming a ray from world-space coordinatesinto the coordinate system of an instanced mesh (object space) e.g., inorder to avoid the computational complexity of transforming theprimitive vertices into world space. It can do so in a MIMD(multiple-instruction, multiple data) fashion, meaning that the rays arehandled independently once inside the traversal coprocessor.

Example Non-Limiting Real Time Interactive Ray Tracing System

FIG. 1 illustrates an example real time ray interactive tracing graphicssystem 100 for generating images using three dimensional (3D) data of ascene or object(s). System 100 includes an input device 110, aprocessor(s) 120, a graphics processing unit(s) (GPU(s)) 130, memory140, and a display(s) 150. The system shown in FIG. 1 can take on anyform factor including but not limited to a personal computer, a smartphone or other smart device, a video game system, a wearable virtual oraugmented reality system, a cloud-based computing system, avehicle-mounted graphics system, a system-on-a-chip (SoC), etc.

The processor 120 may be a multicore central processing unit (CPU)operable to execute an application in real time interactive response toinput device 110, the output of which includes images for display ondisplay 150. Display 150 may be any kind of display such as a stationarydisplay, a head mounted display such as display glasses or goggles,other types of wearable displays, a handheld display, a vehicle mounteddisplay, etc. For example, the processor 120 may execute an applicationbased on inputs received from the input device 110 (e.g., a joystick, aninertial sensor, an ambient light sensor, etc.) and instruct the GPU 130to generate images showing application progress for display on thedisplay 150.

Based on execution of the application on processor 120, the processormay issue instructions for the GPU 130 to generate images using 3D datastored in memory 140. The GPU 130 includes specialized hardware foraccelerating the generation of images in real time. For example, the GPU130 is able to process information for thousands or millions of graphicsprimitives (polygons) in real time due to the GPU's ability to performrepetitive and highly-parallel specialized computing tasks such aspolygon scan conversion much faster than conventional software-drivenCPUs. For example, unlike the processor 120, which may have multiplecores with lots of cache memory that can handle a few software threadsat a time, the GPU 130 may include hundreds or thousands of processingcores or “streaming multiprocessors” (SMs) 132 running in parallel.

In one example embodiment, the GPU 130 includes a plurality ofprogrammable streaming multiprocessors (SMs) 132, and a hardware-basedgraphics pipeline including a graphics primitive engine 134 and a rasterengine 136. These components of the GPU 130 are configured to performreal-time image rendering using a technique called “scan conversionrasterization” to display three-dimensional scenes on a two-dimensionaldisplay 150. In rasterization, geometric building blocks (e.g., points,lines, triangles, quads, meshes, etc.) of a 3D scene are mapped topixels of the display (often via a frame buffer memory).

The GPU 130 converts the geometric building blocks (i.e., polygonprimitives such as triangles) of the 3D model into pixels of the 2Dimage and assigns an initial color value for each pixel. The graphicspipeline may apply shading, transparency, texture and/or color effectsto portions of the image by defining or adjusting the color values ofthe pixels. The final pixel values may be anti-aliased, filtered andprovided to the display 150 for display. Many software and hardwareadvances over the years have improved subjective image quality usingrasterization techniques at frame rates needed for real-time graphics(i.e., 30 to 60 frames per second) at high display resolutions such as4096×2160 pixels or more on one or multiple displays 150.

Traversal Coprocessor Addition to Architecture

To enable the GPU 130 to perform ray tracing in real time in anefficient manner, the GPU is provided with traversal coprocessor 138coupled to one or more SMs 132. The traversal coprocessor 138 includeshardware components configured to perform operations commonly utilizedin ray tracing algorithms A goal of the traversal coprocessor 138 is toaccelerate operations used in ray tracing to such an extent that itbrings the power of ray tracing to real-time graphics application (e.g.,games), enabling high-quality shadows, reflections, and globalillumination. Traversal coprocessor 138, in some example embodiments,includes query-specific traversal hardware 139 that enablesquery-specific programming of the traversal coprocessor's behavior toe.g., increase flexibility and responsiveness of ray tracing operationsto dynamic changes and the like in a scene being rendered. As discussedin more detail below, the result of the traversal coprocessor 138 may beused together with or as an alternative to other graphics relatedoperations performed in the GPU 130.

In the example architecture shown, the new hardware component called a“traversal coprocessor” 138 is used to accelerate certain tasksincluding but not limited to ray tracing. Ray tracing refers to castinga ray into a scene and determining whether and where that ray intersectsthe scene's geometry. This basic ray tracing visibility test is thefundamental primitive underlying a variety of rendering algorithms andtechniques in computer graphics. For example, ray tracing can be usedtogether with or as an alternative to rasterization and z-buffering forsampling scene geometry. It can also be used as an alternative to (or incombination with) environment mapping and shadow texturing for producingmore realistic reflection, refraction and shadowing effects than can beachieved via texturing techniques or other raster “hacks”. To overcomelimitations in image quality that can be achieved with rasterization,system 100 can also generate entire images or parts of images using raytracing techniques. Ray tracing may also be used as the basic primitiveto accurately simulate light transport in physically-based renderingalgorithms such as path tracing, photon mapping, Metropolis lighttransport, and other light transport algorithms.

More specifically, SMs 132 and the traversal coprocessor 138 maycooperate to cast rays into a 3D model and determine whether and wherethat ray intersects the model's geometry. Ray tracing directly simulateslight traveling through a virtual environment or scene. The results ofthe ray intersections together with surface texture, viewing direction,and/or lighting conditions are used to determine pixel color values. Raytracing performed by SMs 132 working with traversal coprocessor 138allows for computer-generated images to capture shadows, reflections,and refractions in ways that can be indistinguishable from photographsor video of the real world. Since ray tracing techniques are even morecomputationally intensive than rasterization due in part to the largenumber of rays that need to be traced, the traversal coprocessor 138 iscapable of accelerating in hardware certain of the morecomputationally-intensive aspects of that process.

In the example non-limiting technology herein, traversal coprocessor 138accelerates both ray-box tests and ray-primitive tests. As part oftraversal, it can also handle at least one level of instance transforms,transforming a ray from world-space coordinates into the coordinatesystem of an instanced mesh. In the example non-limiting embodiments,the traversal coprocessor 138 does all of this in MIMD fashion, meaningthat rays are handled independently once inside the traversalcoprocessor.

In the example non-limiting embodiments, the traversal coprocessor 138operates as a servant (coprocessor) to the SMs (streamingmultiprocessors) 132. In other words, the traversal coprocessor 138 inexample non-limiting embodiments does not operate independently, butinstead follows the commands of the SMs 132 to perform certaincomputationally-intensive ray tracing related tasks much moreefficiently than the SMs 132 could perform themselves.

In the examples shown, the traversal coprocessor 138 receives commandsvia SM 132 instructions and writes results back to an SM register file.For many common use cases (e.g., opaque triangles with at most one levelof instancing), the traversal coprocessor 138 can service the raytracing query without further interaction with the SM 132. Morecomplicated queries (e.g., involving alpha-tested triangles, primitivesother than triangles, or multiple levels of instancing) may requiremultiple round trips. In addition to tracing rays, the traversalcoprocessor 138 is capable of performing more general spatial querieswhere an AABB or the extruded volume between two AABBs (which we call a“beam”) takes the place of the ray. Thus, while the traversalcoprocessor 138 is especially adapted to accelerate ray tracing relatedtasks, it can also be used to perform tasks other than ray tracing.

In addition to the traversal coprocessor 138, the example non-limitingtechnology used to support the system 100 of FIG. 1 provides additionalaccelerated ray tracing enhancements to a number of units as well as asubstantial effort devoted to BVH construction. BVH construction neednot be hardware accelerated (although it may be in some non-limitingembodiments) but could instead be implemented using highly-optimizedsoftware routines running on SMs 132 and/or CPU 120 and/or otherdevelopment systems e.g., during development of an application. Thefollowing exposition describes, among other things, software-visiblebehavior of the traversal coprocessor 138, interfaces to surroundingunits (SMs 132 and the memory subsystem), and additional features thatare part of a complete ray-tracing solution such as certain enhancementsto the group of SMs 132 and the memory caching system.

As discussed above, the traversal coprocessor 138 allows for quicktraversal of an acceleration data structure (e.g., a BVH) to determinewhich primitives (e.g., triangles used for generating a scene) in thedata structure are intersected by a query data structure (e.g., a ray).Example embodiments enable further improvements, such as, capability toselect the traversal behavior based on particular query (e.g., ray)characteristics and/or intersected node characteristics, improvedresponsiveness to dynamic changes in the scene, improved BVH traversalspeeds etc., by providing techniques and systems for query-specificprogramming of the traversal process.

Traversing an Acceleration Data Structure

A good way to accelerate ray tracing is to use an acceleration datastructure. The acceleration data structure represents the 3D model of anobject or a scene in a manner that will help assist in quickly decidingwhich portion of the object a particular ray is likely to intersect andquickly rejecting large portions of the scene the ray will notintersect. A bounding volume hierarchy (BVH) data structure is one typeof acceleration data structure which can help reduce the number ofintersections to test. The BVH data structure represents a scene orobject with a bounding volume and subdivides the bounding volume intosmaller and smaller bounding volumes terminating in leaf nodescontaining geometric primitives. The bounding volumes are hierarchical,meaning that the topmost level encloses the level below it, that levelencloses the next level below it, and so on. In one embodiment, leafnodes can potentially overlap other leaf nodes in the bounding volumehierarchy.

To illustrate how a bounding volume hierarchy works, FIGS. 2A-2G show ateapot recursively subdivided into smaller and smaller hierarchicalbounding volumes. FIG. 2A shows a teapot object, and FIG. 2B shows abounding volume 202 (in this case a box, cube or rectangularparallelepiped) enclosing the whole teapot. The bounding volume 202,which can be efficiently defined by its vertices, provides an indicationof the spatial location of the object and is typically dimensioned to bejust slightly larger than the object.

The first stage in acceleration structure construction acquires thebounding boxes of the referenced geometry. This is achieved by executingfor each geometric primitive in an object a bounding box procedure thatreturns a conservative axis-aligned bounding box for its input primitivesuch as box 202 shown in FIG. 2B. Using these bounding boxes aselementary primitives for the acceleration structures provides thenecessary abstraction to trace rays against arbitrary user-definedgeometry (including several types of geometry within a singlestructure). Because in FIG. 2B the bounding volume 202 is larger thanand completely contains the teapot, a ray that does not intersectbounding volume cannot intersect the teapot, although a ray that doesintersect the bounding volume may or may not intersect the teapot.Because the bounding volume 202 is readily defined by the x,y,zcoordinates of its vertices in 3D space and a ray is defined by itsx,y,z coordinates in 3D space, the ray-bounding volume test to determinewhether a ray intersects the bounding volume 202 is straightforward(although some transform may be used to adjust to different coordinatesystems, as will be explained below).

FIG. 2C, shows the bounding volume 202 subdivided into smaller containedbounding volumes. While the subdivision scheme shown here for purposesof illustration is a so-called 8-ary subdivision or “octree” in whicheach volume is subdivided into eight smaller volumes of uniform size,many other spatial hierarchies and subdivision schemes are known such asa binary tree, a four-ary tree, a k-d tree, a binary space partitioning(BSP) tree, and a bounding volume hierarchy (BVH) tree. See e.g., U.S.Pat. No. 9,582,607.

Each of the subdivided bounding volumes shown in FIG. 2C can be stillfurther subdivided. FIG. 2D shows one of the subdivided volumes 204 ofFIG. 2C being further subdivided to provide additional subdividedencapsulated bounding volumes. As shown in FIG. 2D, some of thesubdivided bounding volumes include portions of the teapot and some donot. Volumes that do not contain a portion of the teapot are not furthersubdivided because the further subdivisions provide no further spatialinformation about the teapot. Already subdivided bounding volumes thatdo include at least one portion of the teapot can be still furtherrecursively subdivided—like the emergence of each of a succession oflittler and littler cats from the hats of Dr. Seuss's' The Cat In TheHat Comes Back (1958). The portions of the space within bounding volume202 that contain geometry are recursively subdivided to permit thetraversal coprocessor 138 to use the volumetric subdivisions toefficiently discover where the geometry is located relative to any givenray. It can be noted that while a spatial or active subdivision of thevolume is possible, many implementations will create the hierarchicalstructure defining volumes and subvolumes ahead of time. In such cases,the builder may often build the hierarchy up from individual trianglesand not down from the whole scene. Building up means you do not need todetermine if some subdivided volume contains anything since bydefinition it contains what is below it in a hierarchy of volumetricsubdivisions.

FIG. 2E shows a further such subdivision of bounding volume 204 into afurther smaller contained bounding volume 206 containing in this examplejust the spout of the teapot plus another surface on the wall of theteapot, and FIG. 2F shows an additional subdivision of bounding volume206 into still smaller contained subdivision 208 encapsulating the endof the teapot's spout. Depending on the way the BVH is constructed,bounding volume 208 can be further and further subdivided as desired—andtraversal coprocessor 138 enables the FIG. 1 system 100 to efficientlytraverse the BVH down to any arbitrary subdivision level. The number andconfigurations of recursive subdivisions will depend on the complexityand configuration of the 3D object being modeled as well as otherfactors such as desired resolution, distance of the object from theviewpoint, etc.

At some level of subdivision (which can be different levels fordifferent parts of the BVH), the traversal coprocessor 138 encountersgeometry making up the encapsulated object being modeled. Using theanalogy of a tree, the successive volumetric subdivisions are the trunk,branches, boughs and twigs, and the geometric is finally revealed at thevery tips of the tree, namely the leaves. In this case, FIG. 2G showsthe surface of the teapot's spout defined by an example mesh ofgeometric primitives. The geometric primitives shown are triangles butother geometric primitives, such as quads, lines, rectangles, quadrics,patches, or other geometric primitives known to those familiar with thestate of the art, may be used (in one embodiment, such other types ofprimitives may be expressed as or converted into triangles). Thegeometric primitives in the mesh represent the shape of the 3D surfaceof the object being modeled. The example shown here is a mesh, butbounded geometry can include discontinuous geometry such as particlesthat may not be connected. In the example non-limiting embodiments, thetraversal coprocessor 138 also accelerates ray intersection tests withthis geometry to quickly determine which triangles are hit by any givenray. Determining ray-primitive intersections involves comparing thespatial xyz coordinates of the vertices of each primitive with the xzycoordinates of the ray to determine whether the ray and the surface theprimitive defines occupy the same space. The ray-primitive intersectiontest can be computationally intensive because there may be manytriangles to test. For example, in the mesh shown in FIG. 2G, the spoutof the teapot alone is made up of over a hundred triangles—although itmay be more efficient in some implementations to further volumetricallysubdivide and thereby limit the number of triangles in any such “leafnode” to something like 16 or fewer.

As discussed above, ray tracing procedures determine what geometricprimitives of a scene are intersected by a ray. However, due to thelarge number of primitives in a 3D scene, it may not be efficient orfeasible to test every geometric primitive for an intersection.Acceleration data structures, such as BVH, allow for quick determinationas to which bounding volumes can be ignored, which bounding volumes maycontain intersected geometric primitives, and which intersectedgeometric primitives matter for visualization and which do not.

Ray Intersection Testing

FIGS. 3A-3C illustrate ray tracing applied to the FIG. 2G boundingvolume 208 including triangle mesh 320. FIG. 3A shows a ray 302 in avirtual space including bounding volumes 310 and 315. To determinewhether the ray 302 intersects one or more triangles in the mesh 320,each triangle could be directly tested against the ray 302. But toaccelerate the process (since the object could contain many thousands oftriangles), the ray 302 is first tested against the bounding volumes 310and 315. If the ray 302 does not intersect a bounding volume, then itdoes not intersect any triangles inside of the bounding volume and alltriangles inside the bounding volume can be ignored for purposes of thatray. Because in FIG. 3A the ray 302 misses bounding volume 310, thetriangles of mesh 320 within that bounding volume need not be tested forintersection. While bounding volume 315 is intersected by the ray 302,bounding volume 315 does not contain any geometry and so no furthertesting is required.

On the other hand, if a ray such as ray 304 shown in FIG. 3B intersectsa bounding volume 310 that contains geometry, then the ray may or maynot intersect the geometry inside of the bounding volume so furthertests need to be performed on the geometry itself to find possibleintersections. Because the rays 304, 306 in FIGS. 3B and 3C intersect abounding volume 310 that contains geometry, further tests need to beperformed to determine whether any (and which) of the primitives insideof the bounding volume are intersected. In FIG. 3B, further testing ofthe intersections with the primitives would indicate that even thoughthe ray 304 passes through the bounding volume 310, it does notintersect any of the primitives the bounding volume encloses(alternatively, as mentioned above, bounding volume 310 could be furthervolumetrically subdivided so that a bounding volume intersection testcould be used to reveal that the ray does not intersect any geometry ormore specifically which primitives the ray may intersect).

FIG. 3C shows a situation in which the bounding volume 310 intersectedby ray 306 and contains geometry that ray 306 intersects. Traversalcoprocessor 138 tests the intersections between the ray 306 and theindividual primitives to determine which primitives the ray intersects.

Ray Tracing Operations

FIG. 4 is a flowchart summarizing example ray tracing operations thetraversal coprocessor 138 performs as described above in cooperationwith SM(s) 132. The FIG. 4 operations are performed by traversalcoprocessor 138 in cooperation with its interaction with an SM 132. Thetraversal coprocessor 138 may thus receive the identification of a rayfrom the SM 132 and traversal state enumerating one or more nodes in oneor more BVH's that the ray must traverse. The traversal coprocessor 138determines which bounding volumes of a BVH data structure the rayintersects (the “ray-complet” test 512) and subsequently whether the rayintersects one or more primitives in the intersected bounding volumesand which triangles are intersected (the “ray-primitive test” 520). Inexample non-limiting embodiments, “complets” (compressed treelets)specify root or interior nodes (i.e., volumes) of the bounding volumehierarchy with children that are other complets or leaf nodes of asingle type per complet.

First, the traversal coprocessor 138 inspects the traversal state of theray. If a stack the traversal coprocessor 138 maintains for the ray isempty, then traversal is complete. If there is an entry on the top ofthe stack, the traversal co-processor 138 issues a request to the memorysubsystem to retrieve that node. The traversal co-processor 138 thenperforms a bounding box test 512 to determine if a bounding volume of aBVH data structure is intersected by a particular ray the SM 132specifies (step 512, 514). If the bounding box test determines that thebounding volume is not intersected by the ray (“No” in step 514), thenthere is no need to perform any further testing for visualization andthe traversal coprocessor 138 can return this result to the requestingSM 132. This is because if a ray misses a bounding volume (as in FIG. 3Awith respect to bounding volume 310), then the ray will miss all othersmaller bounding volumes inside the bounding volume being tested and anyprimitives that bounding volume contains.

If the bounding box test performed by the traversal coprocessor 138reveals that the bounding volume is intersected by the ray (“Yes” inStep 514), then the traversal coprocessor determines if the boundingvolume can be subdivided into smaller bounding volumes (step 518). Inone example embodiment, the traversal coprocessor 138 isn't necessarilyperforming any subdivision itself Rather, each node in the BVH has oneor more children (where each child is a leaf or a branch in the BVH).For each child, there is a bounding volume and a pointer that leads to abranch or a leaf node. When a ray processes a node using traversalcoprocessor 138, it is testing itself against the bounding volumes ofthe node's children. The ray only pushes stack entries onto its stackfor those branches or leaves whose representative bounding volumes werehit. When a ray fetches a node in the example embodiment, it doesn'ttest against the bounding volume of the node—it tests against thebounding volumes of the node's children. The traversal coprocessor 138pushes nodes whose bounding volumes are hit by a ray onto the ray'straversal stack in an order determined by ray configuration. Forexample, it is possible to push nodes onto the traversal stack in theorder the nodes appear in memory, or in the order that they appear alongthe length of the ray, or in some other order. If there are furthersubdivisions of the bounding volume (“Yes” in step 518), then thosefurther subdivisions of the bounding volume are accessed and thebounding box test is performed for each of the resulting subdividedbounding volumes to determine which subdivided bounding volumes areintersected by the ray and which are not. In this recursive process,some of the bounding volumes may be eliminated by test 514 while otherbounding volumes may result in still further and further subdivisionsbeing tested for intersection by traversal coprocessor 138 recursivelyapplying steps 512-518.

Once the traversal coprocessor 138 determines that the bounding volumesintersected by the ray are leaf nodes (“No” in step 518), the traversalcoprocessor performs a primitive (e.g., triangle) intersection test 520to determine whether the ray intersects primitives in the intersectedbounding volumes and which primitives the ray intersects. The traversalcoprocessor 138 thus performs a depth-first traversal of intersecteddescendent branch nodes until leaf nodes are reached. The traversalcoprocessor 138 processes the leaf nodes. If the leaf nodes areprimitive ranges, the traversal coprocessor 138 tests them against theray. If the leaf nodes are instance nodes, the traversal coprocessor 138applies the instance transform. If the leaf nodes are item ranges, thetraversal coprocessor 138 returns them to the requesting SM 132. In theexample non-limiting embodiments, the SM 132 can command the traversalcoprocessor 138 to perform different kinds of ray-primitive intersectiontests and report different results depending on the SMs needs. Forexample, the SM 132 can command the traversal coprocessor 138 to reportthe nearest visible primitive revealed by the intersection test, or toreport all primitives the ray intersects irrespective of whether theyare the nearest visible primitive. The SM 132 can use these differentresults for different kinds of visualization. Once the traversalcoprocessor 138 is done processing the leaf nodes, there may be otherbranch nodes (pushed earlier onto the ray's stack) to test.

Multiple Intersections

In more detail, as shown in FIG. 3C, any given ray may intersectmultiple primitives within a bounding volume. Whether the rayintersection within a given primitive matters for visualization dependson the properties and position of that primitive as well as thevisualization procedures the SM 132 is performing For example,primitives can be opaque, transparent or partially transparent (i.e.,translucent). Opaque primitives will block a ray from passing throughthe primitive because the eye cannot see through the primitive's opaquesurface. Transparent primitives will allow the ray to pass through(because the eye can see through the transparent primitive) but thesituation may be more complex. For example, transparent primitives mayhave specular properties that cause some portion of the ray to reflect(think of reflection from a window pane) and the rest of the ray to passthrough. Other transparent primitives are used to provide a surface ontowhich a texture is mapped. For example, each individual leaf of a treemay be modeled by a transparent primitive onto which an image of theleaf is texture mapped.

FIGS. 5A-5C illustrate some of these scenarios using an example of threetriangles assumed to be in the same bounding volume and each intersectedby a ray. FIG. 5A illustrates a ray directed towards these threetriangles, with the first triangle the ray encounters relative to theviewpoint being opaque. Because the “front” (from the standpoint of thedirection of the ray from the eye) intersected triangle is opaque, thattriangle will block the ray so the ray will not reach the othertriangles even through it spatially intersects them. In this example,the triangles “behind” the opaque triangle from the viewpoint can beignored (culled) after the intersection of the opaque triangle isidentified because the “front”, opaque triangle hides the othertriangles from the user's view along the ray. Culling is indicated bydotted lines in FIGS. 5A-5C. In this case, the traversal coprocessor 138may only need to report the identification of the first, opaque triangleto the SM 132.

FIG. 5B illustrates a ray directed towards the same three triangles butnow the nearest visible triangle is partially transparent rather thanopaque. Because the nearest visible intersected triangle is at leastpartially transparent, the ray may pass through it to hit the opaquetriangle behind it. In this case, the opaque triangle will be visiblethrough the partially transparent triangle but will block the user'sview of the third triangle along the ray. Here, the traversalcoprocessor 138 may report the identification of both front triangles tothe SM 132 but not report the third, culled triangle even though the rayspatially intersects that third triangle. Order of discovery may matterhere. In the case of an alpha and opaque triangle, if the opaque wasfound first, the traversal coprocessor 138 returns the opaque triangleto the SM 132 with traversal state that will resume testing at the alphatriangle. While there is an implication here that the alpha meanstransparent, it really means “return me to the SM 132 and let the SMdetermine how to handle it.” For example, an alpha triangle might betrimmed according to a texture or function so that portions of thetriangle are cut away (i.e., absent, not transparent). The traversalcoprocessor 138 does not know how the SM 132 will handle the alphatriangles (i.e., it does not handle transparent triangles differentlyfrom trimmed triangles). Thus, alpha triangles may or may not block ortint the light arriving from points beyond them along the ray, and inexample embodiments, they require SM 132 intervention tohandle/determine those things.

FIG. 5C illustrates a scenario in which the first two triangles the rayencounters are partially transparent. Because the first and secondintersected triangles are at least partially transparent, the ray willpass through the first and second triangles to impinge upon thealso-intersecting third opaque triangle. Because third intersectedtriangle is opaque, it will block the ray, and the ray will not impingeupon any other triangles behind the third triangle even though they maybe spatially intersected by it. In this case, the traversal coprocessor138 may report all three triangles to the SM 132 but need not report anyfurther triangles behind the opaque triangle because the opaque triangleblocks the ray from reaching those additional triangles.

In some modes, however, the SM 132 may need to know the identities ofall triangles the ray intersects irrespective of whether they are opaqueor transparent. In those modes, the traversal coprocessor 138 can simplyperform the intersection test and return the identities of all trianglesthe ray spatially intersects (in such modes, the traversal coprocessorwill return the same intersection results for all three scenarios shownin FIGS. 5A-5C) and allow the SM 132 to sort it out—or in some casescommand the traversal coprocessor 138 to do more tests on these sametriangles.

As will be discussed in more detail below, when a ray intersects anopaque triangle, the traversal coprocessor 138 can in certain operationsbe programmed to reduce the length of the ray being tested to thelocation of the opaque triangle intersection so it will not report anytriangles “behind” the intersected triangle. When a partiallytransparent triangle is determined to be intersected by a ray, thetraversal coprocessor 138 will return a more complete list of trianglesthe ray impinges upon for purposes of visualization, and the requestingSM 132 may perform further processing to determine whether, based forexample any texture or other properties of the triangle, the ray will beblocked, passed or partially passed and partially reflected. In exampleembodiments, the traversal coprocessor 138 does not have access totexture properties of triangles and so does not attempt to determinevisualization with respect to those properties.

Textures or Other Surface Modifications

For example, FIGS. 6A and 6B show a transparent triangle 610 with atexture 615 of a leaf applied to the triangle. One could think of atriangle made of Plexiglas with a decal of a leaf applied to it. Asshown in FIG. 6A, the ray 620 intersects the transparent triangle 610 ata point that is outside the applied texture 615. Because the ray 620intersects the triangle outside the applied texture 615, the texturewill not block the ray 620 and the ray will pass through the transparenttriangle 610 without obstruction. This is like being able to see throughthe parts of the Plexiglas triangle that are not covered by the leafdecal. Note that in one example embodiment, the SM 132 makes thevisibility determination since the traversal coprocessor 138 does notnecessarily have access to information concerning the leaf decal. Thetraversal coprocessor 138 helps the SM 132 by returning to the SM theidentification of the triangle that the ray intersects along withinformation concerning the properties of that triangle.

In FIG. 6B, the ray 630 intersects the transparent triangle where thetexture 615 is applied. SM 132 will determine whether subsequenttraversal by the traversal coprocessor 138 is necessary or not based onwhether the texture 615 will block the ray 630 or allow the ray 630 topass through. If the ray 630 is blocked by the texture 615, othertriangles behind the transparent triangle 610, which may have otherwisebeen intersected by the ray 630, will be obstructed by the texture andnot contribute to visualization along the ray. In the examplenon-limiting embodiments herein, the traversal coprocessor 138 does nothave access to texture information and so it does not attempt toaccelerate this determination. Traversal coprocessor 138 may for examplereturn to the requesting SM 132 all intersections between the ray andthe various triangles within the object, and the SM may then use thegraphics primitive engine 134 to make further ray tracing visualizationdeterminations. In other example embodiments, traversal coprocessor 138could accelerate some or all of these tests by interacting with thetexture mapping unit and other portions of the 3D graphics pipelinewithin graphics primitive engine 134 to make the necessary visualizationdeterminations.

Coordinate Transforms

FIGS. 2A-3C involve only a single object, namely a teapot. Just as theroom you are in right now contains multiple objects, most 3D scenescontain many objects. For example, a 3D scene containing a teapot willlikely also contain a cup, a saucer, a milk pitcher, a spoon, a sugarbowl, etc. all sitting on a table. In 3D graphics, each of these objectsis typically modeled independently. The graphics system 100 then usescommands from the processor 120 to put all the models together indesired positions, orientations and sizes into the common scene forpurposes of visualization (just as you will set and arrange the tablefor serving tea). What this means is that the SM 132 may commandtraversal processor 138 to analyze the same ray with respect to multipleobjects in the scene. However, the fact that each of these objects willbe transformed in position, orientation and size when placed into thecommon scene is taken into account and accelerated by the traversalcoprocessor 138. In non-limiting example embodiments, the transform fromworld-to-object space is stored in the world space BVH along with aworld-space bounding box. The traversal coprocessor 138 accelerates thetransform process by transforming the ray from world (scene) space intoobject space for purposes of performing the tests shown in FIG. 4. Inparticular, since the transformation of the geometry from object spaceinto world (scene) space is computationally intensive, thattransformation is left to the graphics pipeline graphics primitiveengine 134 and/or raster engine 136 to perform as part of rasterization.The traversal coprocessor 138 instead transforms a given ray from worldspace to the coordinate system of each object defined by an accelerationdata structure and performs its tests in object space.

FIGS. 7A and 7B illustrates how the traversal coprocessor 138 transformssame ray into three different object spaces. FIG. 7A shows three objectson a table: a cup, a teapot and a pitcher. These three objects and atable comprise a scene, which exists in world space. A ray that also isdefined in world space emanates from the viewpoint and intersects eachof the three objects.

FIG. 7B shows each of the three objects as defined in object spaces.Each of these three objects is defined by a respective model that existsin a respective object space. The traversal coprocessor 138 in examplenon-limiting embodiments transforms the ray into the object space ofeach object before performing the intersection tests for that object.This “instance transform” saves the computational effort of transformingthe geometry of each object and the associated volumetric subdivisionsof the acceleration data structure from object space to world space forpurposes of the traversal coprocessor 138 performing intersection tests.

The requesting SM 132 keeps track of which objects are in front of whichother objects with respect to each individual ray and resolvesvisibility in cases where one object hides another object, casts ashadow on another object, and/or reflects light toward another object.The requesting SM 132 can use the traversal processor 138 to accelerateeach of these tests.

Example Tree BVH Acceleration Data Structure

FIGS. 8A and 8B show a recursively-subdivided bounding volume of a 3Dscene (FIG. 8A) and a corresponding tree data structure (FIG. 8B) thatmay be accessed by the traversal coprocessor 138 and used forhardware-accelerated operations performed by traversal coprocessor. Thedivision of the bounding volumes may be represented in a hierarchicaltree data structure with the large bounding volume shown in FIG. 2Brepresented by a parent node of the tree and the smaller boundingvolumes represented by children nodes of the tree that are contained bythe parent node. The smallest bounding volumes are represented as leafnodes in the tree and identify one or more geometric primitivescontained within these smallest bounding volumes.

The tree data structure may be stored in memory outside of the traversalcoprocessor 138 and retrieved based on queries the SMs 132 issue to thetraversal coprocessor 138. The tree data structure includes a pluralityof nodes arranged in a hierarchy. The root nodes N1 of the treestructure correspond to bounding volume N1 enclosing all of thetriangles O1-O8. The root node N1 may identify the vertices of thebounding volume N1 and children nodes of the root node.

In FIG. 8A, bounding volume N1 is subdivided into bounding volumes N2and N3. Children nodes N2 and N3 of the tree structure of FIG. 8Bcorrespond to and represent the bounding volumes N2 and N3 shown in FIG.8A. The children nodes N2 and N3 in the tree data structure identify thevertices of respective bounding volumes N2 and N3 in space. Each of thebounding volumes N2 and N3 is further subdivided in this particularexample. Bounding volume N2 is subdivided into contained boundingvolumes N4 and N5. Bounding volume N3 is subdivided into containedbounding volumes N6 and N7. Bounding volume N7 include two boundingvolumes N8 and N9. Bounding volume N8 includes the triangles O7 and O8,and bounding volume N9 includes leaf bounding volumes N10 and N11 as itschild bounding volumes. Leaf bounding volume N10 includes a primitiverange (e.g., triangle range) O10 and leaf bounding volume N11 includesan item range O9. Respective children nodes N4, N5, N6, N8, N10 and N11of the FIG. 8B tree structure correspond to and represent the FIG. 8Abounding volumes N4, N5, N6, N8, N10 and N11 in space.

The FIG. 8B tree is only three to six levels deep so that volumes N4,N5, N6, N8, N10 and N11 constitute “leaf nodes”—that is, nodes in thetree that have no child nodes. FIG. 8A shows that each of leaf nodebounding volumes N4, N5, N6, and N8, contains two triangles of thegeometry in the scene. For example, volumetric subdivision N4 containstriangles O1 & O2; volumetric subdivision N5 contains triangles O3 & O4;volumetric subdivision N6 contains trials O5 & O6; and volumetricsubdivision N8 contains triangles O7 & O8. The tree structure shown inFIG. 8B represents these leaf nodes N4, N5, N6, and N7 by associatingthem with the appropriate ones of triangles O1-O8 of the scene geometry.To access this scene geometry, the traversal coprocessor 138 traversesthe tree data structure of FIG. 8B down to the leaf nodes. In general,different parts of the tree can and will have different depths andcontain different numbers of triangles. Leaf nodes associated withvolumetric subdivisions that contain no geometry need not be explicitlyrepresented in the tree data structure (i.e., the tree is “trimmed”).

According to some embodiments, the subtree rooted at N7 may represent aset of bounding volumes or BVH that is defined in a different coordinatespace than the bounding volumes corresponding to nodes N1-N3. Whenbounding volume N7 is in a different coordinate space from its parentbounding volume N3, an instance node N7′ which provides the raytransformation necessary to traverse the subtree rooted at N7, mayconnect the rest of the tree to the subtree rooted at N7. Instance nodeN7′ connects the bounding volume or BVH corresponding to nodes N1-N3,with the bounding volumes or BVH corresponding to nodes N7 etc. bydefining the transformation from the coordinate space of N1-N3 (e.g.,world space) to the coordinate space of N7 etc. (e.g., object space).

The Internal Structure and Operation of Traversal Coprocessor 138

FIG. 9 shows an example simplified block diagram of traversalcoprocessor 138 including hardware configured to perform acceleratedtraversal operations as described above (a still more detailedimplementation of this traversal coprocessor 138 is described below).Because the traversal coprocessor 138 shown in FIG. 9 is adapted totraverse tree-based acceleration data structures such as shown in FIGS.8A, 8B, it may also be called a “tree traversal unit” or “TTU” 700 (the700 reference number is used to refer to the more detailed non-limitingimplementation of traversal coprocessor 138 shown in FIG. 1). Treetraversal operations may include, for example, determining whether a rayintersects bounding volumes and/or primitives of a tree data structure(e.g., a BVH tree), which tests may involve transforming the ray intoobject space.

The TTU 700 includes dedicated hardware to determine whether a rayintersects bounding volumes and dedicated hardware to determine whethera ray intersects primitives of the tree data structure. In someembodiments, the TTU 700 may perform a depth-first traversal of abounding volume hierarchy using a short stack traversal withintersection testing of supported leaf node primitives and mid-traversalreturn of alpha primitives and unsupported leaf node primitives (items).The intersection of primitives will be discussed with reference totriangles, but other geometric primitives may also be used.

In more detail, TTU 700 includes an intersection management block 722, aray management block 730 and a stack management block 740. Each of theseblocks (and all of the other blocks in FIG. 9) may constitute dedicatedhardware implemented by logic gates, registers, hardware-embedded lookuptables or other combinatorial logic, etc.

The ray management block 730 is responsible for managing informationabout and performing operations concerning a ray specified by an SM 132to the ray management block. The stack management block 740 works inconjunction with traversal logic 712 to manage information about andperform operations related to traversal of a BVH acceleration datastructure. Traversal logic 712 is directed by results of a ray-complettest block 710 that tests intersections between the ray indicated by theray management block 730 and volumetric subdivisions represented by theBVH, using instance transforms as needed. The ray-complet test block 710retrieves additional information concerning the BVH from memory 140 viaan L0 complet cache 752 that is part of the TTU 700. The results of theray-complet test block 710 informs the traversal logic 712 as to whetherfurther recursive traversals are needed. The stack management block 740maintains stacks to keep track of state information as the traversallogic 712 traverses from one level of the BVH to another, with the stackmanagement block pushing items onto the stack as the traversal logictraverses deeper into the BVH and popping items from the stack as thetraversal logic traverses upwards in the BVH. The stack management block740 is able to provide state information (e.g., intermediate or finalresults) to the requesting SM 132 at any time the SM requests.

The intersection management block 722 manages information about andperforms operations concerning intersections between rays andprimitives, using instance transforms as needed. The ray-primitive testblock 720 retrieves information concerning geometry from memory 140 onan as-needed basis via an L0 primitive cache 754 that is part of TTU700. The intersection management block 722 is informed by results ofintersection tests the ray-primitive test and transform block 720performs. Thus, the ray-primitive test and transform block 720 providesintersection results to the intersection management block 722, whichreports geometry hits and intersections to the requesting SM 132.

A Stack Management Unit 740 inspects the traversal state to determinewhat type of data needs to be retrieved and which data path (complet orprimitive) will consume it. The intersections for the bounding volumesare determined in the ray-complet test path of the TTU 700 including oneor more ray-complet test blocks 710 and one or more traversal logicblocks 712. A complet specifies root or interior nodes of a boundingvolume. Thus, a complet may define one or more bounding volumes for theray-complet test. The ray-complet test path of the TTU 700 identifieswhich bounding volumes are intersected by the ray. Bounding volumesintersected by the ray need to be further processed to determine if theprimitives associated with the intersected bounding volumes areintersected. The intersections for the primitives are determined in theray-primitive test path including one or more ray-primitive test andtransform blocks 720 and one or more intersection management blocks 722.

The TTU 700 receives queries from one or more SMs 132 to perform treetraversal operations. The query may request whether a ray intersectsbounding volumes and/or primitives in a BVH data structure. The querymay identify a ray (e.g., origin, direction, and length of the ray) anda BVH data structure and traversal state (e.g., short stack) whichincludes one or more entries referencing nodes in one or more BoundingVolume Hierarchies that the ray is to visit. The query may also includeinformation for how the ray is to handle specific types of intersectionsduring traversal. The ray information may be stored in the raymanagement block 730. The stored ray information (e.g., ray length) maybe updated based on the results of the ray-primitive test.

The TTU 700 may request the BVH data structure identified in the queryto be retrieved from memory outside of the TTU 700. Retrieved portionsof the BVH data structure may be cached in the level-zero (L0) cache 750within the TTU 700 so the information is available for othertime-coherent TTU operations, thereby reducing memory 140 accesses.Portions of the BVH data structure needed for the ray-complet test maybe stored in a L0 complet cache 752 and portions of the BVH datastructure needed for the ray-primitive test may be stored in an L0primitive cache 754.

After the complet information needed for a requested traversal step isavailable in the complet cache 752, the ray-complet test block 710determines bounding volumes intersected by the ray. In performing thistest, the ray may be transformed from the coordinate space of thebounding volume hierarchy to a coordinate space defined relative to acomplet. The ray is tested against the bounding boxes associated withthe child nodes of the complet. In the example non-limiting embodiment,the ray is not tested against the complet's own bounding box because (1)the TTU 700 previously tested the ray against a similar bounding boxwhen it tested the parent bounding box child that referenced thiscomplet, and (2) a purpose of the complet bounding box is to define alocal coordinate system within which the child bounding boxes can beexpressed in compressed form. If the ray intersects any of the childbounding boxes, the results are pushed to the traversal logic todetermine the order that the corresponding child pointers will be pushedonto the traversal stack (further testing will likely require thetraversal logic 712 to traverse down to the next level of the BVH).These steps are repeated recursively until intersected leaf nodes of theBVH are encountered

The ray-complet test block 710 may provide ray-complet intersections tothe traversal logic 612. Using the results of the ray-complet test, thetraversal logic 712 creates stack entries to be pushed to the stackmanagement block 740. The stack entries may indicate internal nodes(i.e., a node that includes one or more child nodes) that need to befurther tested for ray intersections by the ray-complet test block 710and/or triangles identified in an intersected leaf node that need to betested for ray intersections by the ray-primitive test and transformblock 720. The ray-complet test block 710 may repeat the traversal oninternal nodes identified in the stack to determine all leaf nodes inthe BVH that the ray intersects. The precise tests the ray-complet testblock 710 performs will in the example non-limiting embodiment bedetermined by mode bits, ray operations (see below) and culling of hits,and the TTU 700 may return intermediate as well as final results to theSM 132.

The intersected leaf nodes identify primitives that may or may not beintersected by the ray. One option is for the TTU 700 to provide e.g., arange of geometry identified in the intersected leaf nodes to the SM 132for further processing. For example, the SM 132 may itself determinewhether the identified primitives are intersected by the ray based onthe information the TTU 700 provides as a result of the TTU traversingthe BVH. To offload this processing from the SM 132 and therebyaccelerate it using the hardware of the TTU 700, the stack managementblock 740 may issue requests for the ray-primitive and transform block720 to perform a ray-primitive test for the primitives withinintersected leaf nodes the TTU's ray-complet test block 710 identified.In some embodiments, the SM 132 may issue a request for theray-primitive test to test a specific range of primitives and transformblock 720 irrespective of how that geometry range was identified.

After making sure the primitive data needed for a requestedray-primitive test is available in the primitive cache 754, theray-primitive and transform block 710 may determine primitives that areintersected by the ray using the ray information stored in the raymanagement block 730. The ray-primitive test block 720 provides theidentification of primitives determined to be intersected by the ray tothe intersection management block 722.

The intersection management block 722 can return the results of theray-primitive test to the SM 132. The results of the ray-primitive testmay include identifiers of intersected primitives, the distance ofintersections from the ray origin and other information concerningproperties of the intersected primitives. In some embodiments, theintersection management block 722 may modify an existing ray-primitivetest (e.g., by modifying the length of the ray) based on previousintersection results from the ray-primitive and transform block 710.

The intersection management block 722 may also keep track of differenttypes of primitives. For example, the different types of trianglesinclude opaque triangles that will block a ray when intersected andalpha triangles that may or may not block the ray when intersected ormay require additional handling by the SM. Whether a ray is blocked ornot by a transparent triangle may for example depend on texture(s)mapped onto the triangle, area of the triangle occupied by the texture(see FIGS. 6A and 6B) and the way the texture modifies the triangle. Forexample, transparency (e.g., stained glass) in some embodiments requiresthe SM 132 to keep track of transparent object hits so they can besorted and shaded in ray-parametric order, and typically don't actuallyblock the ray. Meanwhile, alpha “trimming” allows the shape of theprimitive to be trimmed based on the shape of a texture mapped onto theprimitive—for example, cutting a leaf shape out of a triangle. (Notethat in raster graphics, transparency is often called “alpha blending”and trimming is called “alpha test”). In other embodiments, the TTU 700can push transparent hits to queues in memory for later handling by theSM 132 and directly handle trimmed triangles by sending requests to thetexture unit. Each triangle may include a designator to indicate thetriangle type. The intersection management block 722 is configured tomaintain a result queue for tracking the different types of intersectedtriangles. For example, the result queue may store one or moreintersected opaque triangle identifiers in one queue and one or moretransparent triangle identifiers in another queue.

For opaque triangles, the ray intersection can be fully determined inthe TTU 700 because the area of the opaque triangle blocks the ray fromgoing past the surface of the triangle. For transparent triangles, rayintersections cannot in some embodiments be fully determined in the TTU700 because TTU 700 performs the intersection test based on the geometryof the triangle and may not have access to the texture of the triangleand/or area of the triangle occupied by the texture (in otherembodiments, the TTU may be provided with texture information by thetexture mapping block of the graphics pipeline). To fully determinewhether the triangle is intersected, information about transparenttriangles the ray-primitive and transform block 710 determines areintersected may be sent to the SM 132, for the SM to make the fulldetermination as to whether the triangle affects visibility along theray.

The SM 132 can resolve whether or not the ray intersects a textureassociated with the transparent triangle and/or whether the ray will beblocked by the texture. The SM 132 may in some cases send a modifiedquery to the TTU 700 (e.g., shortening the ray if the ray is blocked bythe texture) based on this determination.

In one embodiment, the TTU 700 may be configured to return all trianglesdetermined to intersect the ray to the SM 132 for further processing.Because returning every triangle intersection to the SM 132 for furtherprocessing is costly in terms of interface and thread synchronization,the TTU 700 may be configured to hide triangles which are intersectedbut are provably capable of being hidden without a functional impact onthe resulting scene. For example, because the TTU 700 is provided withtriangle type information (e.g., whether a triangle is opaque ortransparent), the TTU 700 may use the triangle type information todetermine intersected triangles that are occluded along the ray byanother intersecting opaque triangle and which thus need not be includedin the results because they will not affect the visibility along theray. As discussed above with reference to FIGS. 5A-5C, if the TTU 700knows that a triangle is occluded along the ray by an opaque triangle,the occluded triangle can be hidden from the results without impact onvisualization of the resulting scene.

The intersection management block 722 may include a result queue forstoring hits that associate a triangle ID and information about thepoint where the ray hit the triangle. When a ray is determined tointersect an opaque triangle, the identity of the triangle and thedistance of the intersection from the ray origin can be stored in theresult queue. If the ray is determined to intersect another opaquetriangle, the other intersected opaque triangle can be omitted from theresult if the distance of the intersection from the ray origin isgreater than the distance of the intersected opaque triangle alreadystored in the result queue. If the distance of the intersection from theray origin is less than the distance of the intersected opaque trianglealready stored in the result queue, the other intersected opaquetriangle can replace the opaque triangle stored in the result queue.After all of the triangles of a query have been tested, the opaquetriangle information stored in the result queue and the intersectioninformation may be sent to the SM 132.

In some embodiments, once an opaque triangle intersection is identified,the intersection management block 722 may shorten the ray stored in theray management block 730 so that bounding volumes (which may includetriangles) behind the intersected opaque triangle (along the ray) willnot be identified as intersecting the ray.

The intersection management block 722 may store information aboutintersected transparent triangles in a separate queue. The storedinformation about intersected transparent triangles may be sent to theSM 132 for the SM to resolve whether or not the ray intersects a textureassociated with the triangle and/or whether the texture blocks the ray.The SM may return the results of this determination to the TTU 700and/or modify the query (e.g., shorten the ray if the ray is blocked bythe texture) based on this determination.

Example Ray Tracing Shading Pipeline

FIG. 10A shows an exemplary ray tracing shading pipeline 900 that may beperformed by SM 132 and accelerated by TTU 700. The ray tracing shadingpipeline 900 starts by an SM 132 invoking ray generation 910 and issuinga corresponding ray tracing request to the TTU 700. The ray tracingrequest identifies a single ray cast into the scene and asks the TTU 700to search for intersections with an acceleration data structure the SM132 also specifies. The TTU 700 traverses (FIG. 10A block 920) theacceleration data structure to determine intersections or potentialintersections between the ray and the volumetric subdivisions andassociated triangles the acceleration data structure represents.Potential intersections can be identified by finding bounding volumes inthe acceleration data structure that are intersected by the ray.Descendants of non-intersected bounding volumes need not be examined.

For triangles within intersected bounding volumes, the TTU 700ray-primitive test block 720 performs an intersection 930 process todetermine whether the ray intersects the primitives. The TTU 700 returnsintersection information to the SM 132, which may perform an “any hit”shading operation 940 in response to the intersection determination. Forexample, the SM 132 may perform (or have other hardware perform) atexture lookup for an intersected primitive and decide based on theappropriate texel's value how to shade a pixel visualizing the ray. TheSM 132 keeps track of such results since the TTU 700 may return multipleintersections with different geometry in the scene in arbitrary order.

Alternatively, primitives that the TTU 700 determines are intersectedmay be further processed to determine 950 whether they should be shadedas a miss 960 or as a closest hit 970. The SM 132 can for exampleinstruct the TTU 700 to report a closest hit in the specified geometry,or it may instruct the TTU to report all hits in the specified geometry.For example, it may be up to the SM 132 to implement a “miss” shadingoperation for a primitive the TTU 700 determines is intersected based onimplemented environment lookups (e.g., approximating the appearance of areflective surface by means of a precomputed texture image) such asshown in FIGS. 6A & 6B. The SM 132 may perform a closest hit shadingoperation to determine the closest intersected primitive based onmaterial evaluations and texture lookups in response to closest hitreports the TTU 700 provided for particular object geometry.

The FIG. 10B more detailed diagram of ray-tracing pipeline flowchartshows the data flow and interaction between components for arepresentative use case: tracing rays against a scene containinggeometric primitives, with instance transformations handled in hardware.In one example non-limiting embodiment, the ray-tracing pipeline of FIG.10B is essentially software-defined (which in example embodiments meansit is determined by the SMs 132) but makes extensive use of hardwareacceleration by TTU 700. Key components include the SM 132 (and the restof the compute pipeline), the TTU 700 (which serves as a coprocessor toSM), and the L1 cache and downstream memory system, from which the TTUfetches BVH and triangle data.

The pipeline shown in FIG. 10B shows that bounding volume hierarchycreation 1002 can be performed ahead of time by a development system. Italso shows that ray creation and distribution 1004 are performed orcontrolled by the SM 132 or other software in the example embodiment, asis shading (which can include lighting and texturing). The examplepipeline includes a “top level” BVH tree traversal 1006, raytransformation 1014, “bottom level” BVH tree traversal 1018, and aray/triangle (or other primitive) intersection 1026 that are eachperformed by the TTU 700. These do not have to be performed in the ordershown, as handshaking between the TTU 700 and the SM 132 determines whatthe TTU 700 does and in what order.

The SM 132 presents one or more rays to the TTU 700 at a time. Each raythe SM 132 presents to the TTU 700 for traversal may include the ray'sgeometric parameters, traversal state, and the ray's ray flags, modeflags and ray operations information. In an example embodiment, a rayoperation (RayOp) provides or comprises an auxiliary arithmetic and/orlogical test to suppress, override, and/or allow storage of anintersection. The traversal stack may also be used by the SM 132 tocommunicate certain state information to the TTU 700 for use in thetraversal. A new ray query may be started with an explicit traversalstack. For some queries, however, a small number of stack initializersmay be used instead of specifying an explicit stack for beginning thenew query of a given type, such as, for example: traversal starting froma complet; intersection of a ray with a range of triangles; intersectionof a ray with a range of triangles, followed by traversal starting froma complet; vertex fetch from a triangle buffer for a given triangle,etc. In some embodiments, using stack initializers instead of explicitstack initialization improves performance because stack initializersrequire fewer streaming processor registers and reduce the number ofparameters that need to be transmitted from the streaming processor tothe TTU.

In the example embodiment, a set of mode flags the SM 132 presents witheach query (e.g., ray) may at least partly control how the TTU 700 willprocess the query when the query intersects the bounding volume of aspecific type or intersects a primitive of a specific primitive type.The mode flags the SM 132 provides to the TTU 700 enable the ability bythe SM and/or the application to e.g., through a RayOp, specify anauxiliary arithmetic or logical test to suppress, override, or allowstorage of an intersection. The mode flags may for example enabletraversal behavior to be changed in accordance with such aspects as, forexample, a depth (or distance) associated with each bounding volumeand/or primitive, size of a bounding volume or primitive in relation toa distance from the origin or the ray, particular instances of anobject, etc. This capability can be used by applications to dynamicallyand/or selectively enable/disable sets of objects for intersectiontesting versus specific sets or groups of queries, for example, to allowfor different versions of models to be used when application statechanges (for example, when doors open or close) or to provide differentversions of a model which are selected as a function of the length ofthe ray to realize a form of geometric level of detail, or to allowspecific sets of objects from certain classes of rays to make somelayers visible or invisible in specific views.

In addition to the set of mode flags which may be specified separatelyfor the ray-complet intersection and for ray-primitive intersections,the ray data structure may specify other RayOp test related parameters,such as ray flags, ray parameters and a RayOp test. The ray flags can beused by the TTU 700 to control various aspects of traversal behavior,back-face culling, and handling of the various child node types, subjectto a pass/fail status of an optional RayOp test. RayOp tests addflexibility to the capabilities of the TTU 700, at the expense of somecomplexity. The TTU 700 reserves a “ray slot” for each active ray it isprocessing, and may store the ray flags, mode flags and/or the RayOpinformation in the corresponding ray slot buffer within the TTU duringtraversal.

In the example shown in FIG. 10B, the TTU 700 performs a top level treetraversal 1006 and a bottom level tree traversal 1018. In the exampleembodiment, the two level traversal of the BVH enables fast ray tracingresponses to dynamic scene changes.

Ray transformation 1014 provides the appropriate transition from the toplevel tree traversal 1006 to the bottom level tree traversal 1018 bytransforming the ray, which may be used in the top level traversal in afirst coordinate space (e.g., world space), to a different coordinatespace (e.g., object space) of the BVH of the bottom level traversal. Anexample BVH traversal technique using a two level traversal is describedin previous literature, see, e.g., Woop, “A Ray Tracing HardwareArchitecture for Dynamic Scenes”, Universitat des Saarlandes, 2004, butembodiments are not limited thereto.

In some embodiments, the top level traversal (in world space) is made ina BVH that may be dynamically recalculated (e.g., by SM 132) in responseto changes in the position or orientation of instanced objects, and thebottom level traversal is made in a BVH of bounding volumes that remainstatic or substantially static. Changes in the shape of geometry in thelower-level BVH which do not alter the bounding box of the root node ofthat lower-level BVH require no changes in the top-level BVH. Thebounding volumes in the BVH used for the bottom level tree traversal1018 (in object space) may encompass more detailed information regardingthe scene geometry than the respective bounding volumes used in the toplevel tree traversal 1006, thereby avoiding or at least reducing themodification of the bottom level traversal BVH in response to scenechanges. This helps to speed up ray tracing of dynamic scenes.

The top level tree traversal 1006 by TTU 700 receives complets from theL1 cache 1012, and provides an instance to the ray transformation 1014for transformation or a miss/end output 1013 to the SM 132 for closesthit shader 1015 processing by the SM (this block can also operaterecursively based on non-leaf nodes/no hit conditions). In the top leveltree traversal 1006, a next complet fetch step 1008 fetches the nextcomplet to be tested for ray intersection in step 1010 from the memoryand/or cache hierarchy and ray-bounding volume intersection testing isdone on the bounding volumes in the fetched complet. In exampleembodiments, instance nodes are considered leaf nodes and get processedin top-level traversal. The example non-limiting TTU is able toencounter and process primitive ranges and item ranges in the top-levelBVH. Each traversal step of each ray starts with the stack managementunit inspecting the currently active stack of an active ray. In toplevel tree traversal, the top-level stack is active, and thus the stackmanagement unit inspects the top level stack. If the top-level stack isactive and empty, then the ray and its result queue are returned to theSM. Otherwise, the Stack Management Unit obtains the address of the nextcomplet or leaf to be processed by that ray and requests thatcomplet/leaf from the memory subsystem via the L0/L1 caches. Ifbottom-level tree traversal, the bottom-level stack is active, and thusthe stack management unit inspects the bottom level stack. If thebottom-level stack is active and empty, then the ray switches totop-level traversal and the top-level stack becomes the active stack.Traversal can thus continue in the bottom level (the continuation in thetop level occurs when the bottom level stack becomes empty).

As described above, an instance node connects one BVH to another BVHwhich is in a different coordinate system. When a child of theintersected bounding volume is an instance node, the ray transformation1014 is able to retrieve an appropriate transform matrix from the L1cache 1016. The TTU 700, using the appropriate transform matrix,transforms the ray to the coordinate system of the child BVH. U.S.patent application Ser. No. 14/697,480, which is already incorporated byreference, describes transformation nodes that connect a first set ofnodes in a tree to a second set of nodes where the first and second setsof nodes are in different coordinate systems. The instance nodes inexample embodiments may be similar to the transformation nodes in U.S.application Ser. No. 14/697,480. In an alternative, non-instancing modeof TTU 700 shown in FIG. 10C, the TTU does not execute a “bottom” leveltree traversal 1018 and noninstanced tree BVH traversals are performedby blocks 1008, 1010 e.g., using only one stack. The TTU 700 can switchbetween the FIG. 10B instanced operations and the FIG. 10C non-instancedoperations based on what it reads from the BVH and/or query type. Forexample, a specific query type may restrict the TTU to use just thenon-instanced operations. In such a query, any intersected instancenodes would be returned to the SM.

In some non-limiting embodiments, ray-bounding volume intersectiontesting in step 1010 is performed on each bounding volume in the fetchedcomplet before the next complet is fetched. Other embodiments may useother techniques, such as, for example, traversing the top leveltraversal BVH in a depth-first manner. U.S. Pat. No. 9,582,607, alreadyincorporated by reference, describes one or more complet structures andcontents that may be used in example embodiments. U.S. Pat. No.9,582,607 also describes an example traversal of complets.

When the RCT unit determines that a ray intersects a child boundingvolume, the Tree Traversal unit records a pointer or reference to thecorresponding child complet or leaf node for subsequent testing againstthe ray. In example embodiments, one or more stack data structures(e.g., the traversal stack illustrated in FIG. 12) is used for keepingtrack of complet or leaf nodes to be subsequently tested forintersection with the ray. In some example embodiments, a traversalstack of a small size may be used to keep track of complets to betraversed by operation of the top level tree traversal 1006, andprimitives to be tested for intersection, and a larger local stack datastructure can be used to keep track of the traversal state in the bottomlevel tree traversal 1018. In some example embodiments, the traversalstacks for both the top level traversal and the bottom level traversalmay be short, i.e., limited to a small size (e.g., 4 entries each), tofacilitate efficient passing of stack information between the traversalcoprocessor and the SM. In some example embodiments, the top-level andbottom-level stacks are equivalently sized, and both leaf nodes andcomplets may be present in both the top-level and bottom-level BVHs. Insome example embodiments, there is an option to limit the stack contentexchanged between the traversal coprocessor and the SM (the number ofstack entries that may be exchanged may be configurable independently ofthe stack depth). If the number of stack entries that can be exchangedbetween traversal coprocessor and the SM is limited, he entire stack maynevertheless be available for traversal, and the ways in which the stackis used may be limited. For example, a use limit could be that the leafnodes pushed onto the stack may not exceed the stack limit minus one,except for the case of all opaque triangles which may be guaranteed topop off the stack before the return from traversal.

In example embodiments, while bottom-level BVH traversal is active, theposition and direction of the ray in the upper level BVH are storedseparately from the transformed position and direction used fortraversing the bottom level BVH. In the bottom level tree traversal1018, a next complet fetch step 1022 fetches the next complet to betested for ray intersection in step 1024 from the memory and/or cachehierarchy 1020 and ray-bounding volume intersection testing is done onthe bounding volumes in the fetched complet. The bottom level treetraversal, as noted above, may include complets with bounding volumes ina different coordinate system than the bounding volumes traversed in theupper level tree traversal. The bottom level tree traversal alsoreceives complets from the L1 cache and can operate recursively oriteratively within itself based on non-leaf/no-hit conditions and alsowith the top level tree traversal 1006 based on miss/end detection.Intersections of the ray with the bounding volumes in the lower levelBVH may be determined with the ray transformed to the coordinate systemof the lower level complet retrieved. The leaf bounding volumes found tobe intersected by the ray in the lower level tree traversal are thenprovided to the ray/triangle intersection 1026.

As mentioned above, leaf nodes can be processed in both top-level andbottom-level traversal in example non-limiting embodiments. For example,the leaf outputs of the bottom level tree traversal 1018 can be providedto the ray/triangle intersection 1026 (which has L0 cache access as wellas ability to retrieve triangles via the L1 cache 1028). Theray/triangle intersection 1026 may also receive leaf outputs from thetop level tree traversal 1006 when certain leaf nodes are reachedwithout traversing an instanced BVH. The L0 complet and triangle cachesmay be small read-only caches internal to the TTU 700.

After all the primitives in the primitive range have been processed, theIntersection Management Unit inspects the state of the result queue andcrafts packets to send to the Stack Management Unit and/or RayManagement Unit to update the ray's attributes and traversal state, setup the ray's next traversal step, and/or return the ray to the SM 132(if necessary). If the result queue contains opaque or alphaintersections found during the processing of the primitive range thenthe Intersection Management Unit signals the parametric length (t) ofthe nearest opaque intersection in the result queue to the raymanagement unit to record as the ray's tmax to shorten the ray. Toupdate the traversal state to set up the ray's next traversal step theIntersection Management Unit signals to the Stack Management Unitwhether an opaque intersection from the primitive range is present inthe result queue, whether one or more alpha intersections are present inthe result queue, whether the result queue is full, whether additionalalpha intersections were found in the primitive range that have not beenreturned to the SM and which are not present in the result queue, andthe index of the next alpha primitive in the primitive range for the rayto test after the SM consumes the contents of the result queue (theindex of the next primitive in the range after the alpha primitive withthe highest memory-order from the current primitive range in the resultqueue).

When the Stack Management Unit 740 receives the packet from IntersectionManagement Unit 722, the Stack Management Unit 740 inspects the packetto determine the next action required to complete the traversal step andstart the next one. If the packet from Intersection Management Unit 722indicates an opaque intersection has been found in the primitive rangeand the ray mode bits indicate the ray is to finish traversal once anyintersection has been found the Stack Management Unit 740 returns theray and its results queue to the SM with traversal state indicating thattraversal is complete (a done flag set and/or an empty top level andbottom level stack). If the packet from Intersection Management Unit 722indicates that there opaque or alpha intersection in the result queueand that there are remaining alpha intersections in the primitive rangenot present in the result queue that were encountered by the ray duringthe processing of the primitive range that have not already beenreturned to the SM, the Stack Management Unit 740 returns the ray andthe result queue to the SM with traversal state modified to set the cullopaque bit to prevent further processing of opaque primitives in theprimitive range and the primitive range starting index advanced to thefirst alpha primitive after the highest alpha primitive intersectionfrom the primitive range returned to the SM in the ray's result queue.If the packet from Intersection Management Unit 722 indicates that noopaque or alpha intersections were found when the ray processed theprimitive range the Stack Management Unit 740 pops the top of stackentry (corresponding to the finished primitive range) off the activetraversal stack. If the packet from Stack Management Unit 740 indicatesor that either there are opaque intersections in the result queue andthe ray mode bits do not indicate that the ray is to finish traversalonce any intersection has been found and/or there are alphaintersections in the result queue, but there were no remaining alphaintersections found in the primitive range not present in the resultqueue that have not already been returned to the SM the Stack ManagementUnit 740 pops the top of stack entry (corresponding to the finishedprimitive range) off the active traversal stack and modifies thecontents of the result queue to indicate that all intersections presentin the result queue come from a primitive range whose processing wascompleted.

If the active stack is the bottom stack, and the bottom stack is emptythe Stack Management Unit 740 sets the active stack to the top stack. Ifthe top stack is the active stack, and the active stack is empty, thenthe Stack Management Unit 740 returns the ray and its result queue tothe SM with traversal state indicating that traversal is complete (adone flag set and/or an empty top level and bottom level stack). If theactive stack contains one or more stack entries, then the StackManagement Unit 740 inspects the top stack entry and starts the nexttraversal step. Testing of primitive and/or primitive ranges forintersections with a ray and returning results to the SM 132 aredescribed in co-pending U.S. application Ser. No. ______ entitled“Conservative Watertight Ray Triangle Intersection” (Atty. Dkt. 6610-36(18-SC-0145)), U.S. application Ser. No. ______ entitled “Method forContinued Bounding Volume Hierarchy Traversal on Intersection withoutShader Intervention” (Atty. Dkt. 6610-32 (18-AU-0127)) and U.S.application Ser. No. ______ entitled “Method for Handling Out-of-OrderOpaque and Alpha Ray/Primitive Intersections” (Atty. Dkt. 6610-37(18-AU-0149)), which are hereby incorporated by reference in theirentireties.

While the above disclosure is framed in the specific context of computergraphics and visualization, ray tracing and the disclosed traversalcoprocessor could be used for a variety of applications beyond graphicsand visualization. Non-limiting examples include sound propagation forrealistic sound synthesis, simulation of sonar systems, design ofoptical elements and systems, particle transport simulation (e.g., formedical physics or experimental high-energy physics), general wavepropagation simulation, comparison to LIDAR data for purposes e.g., ofrobot or vehicle localization, and others. OptiX™ has already been usedfor some of these application areas in the past.

Rays are traced under different circumstances and for a variety ofreasons. It is desirable to be able to trace different types of rayswith constraints to limit traversal to specific subsets of the BVH or toonly test rays against certain subsets of primitives for intersection.Examples of these circumstances might include changes in object statesaffecting geometry (e.g., gates or doors opening/closing) or shading(e.g., traffic lights changing), multiple versions of the same objectwith different geometric or shading level of detail being selected as afunction of the number of bounces along a path or accumulated pathlength, omitting alpha primitives or items, or highlighting objects inspecific “layers” of a CAD application.

However, changes in objects and/or the scene to be represented may oftenrequire the BVH or portions thereof to be modified and/or regenerated atruntime. Regenerating or even modifying the BVH corresponding to a scenemay be time consuming For example, as described above, each boundingvolume in the BVH may encompass many other bounding volumes, and up tomillions of geometric primitives. Thus, techniques are needed forimproving the performance of ray tracing systems when dynamic scenechanges are to be rendered.

In some applications, changes in a scene and/or aspects of visualizationmay not require all parts of the scene to be regenerated in the BVH.Although for many types of scene changes, rebuilding of the BVH or partsthereof may be required, in some instances the changes are such thatrebuilding or modification of the BVH can be minimized or avoided in theinterest of time. In some applications, a change in a scene, such as forexample, the closing of an open door, and the resulting closing off fromview an inside of a room that was earlier in view, may not require theBVH to be changed or regenerated if the ray can dynamically determinehow to choose between different instances or configurations of the sameobject represented in the same BVH. Some example embodiments providetechniques to handle scene changes efficiently. Some other techniques,such as, for example, instancing of BVH nodes, help control changes tothe BVH when scene changes occur. When instanced objects change positionand/or orientation without changing shape, we only need to change theinstance node's transformation coefficients and bounding box (and anyancestor complet bounding boxes that fail to bound the new bounding boxfor the instance node). This is less work than transforming eachprimitive and inserting it into a world-space BVH.

Conventional ray tracers perform traversal of the acceleration datastructure solely on the basis of the geometric attributes of the ray,acceleration data structure, and primitives. While many ray tracersprovide support for alpha primitives or transparency, they do so withinthe context of post-traversal shading. That is, although many raytracers provide for certain types of objects (e.g., a cluster of leavesof a tree and like objects that are not entirely opaque throughout) tobe modeled as transparent primitives, after an initial determinationduring traversal of the BVH that a transparent object may intersect aray, the definitive determination is made outside of that traversal. Inorder to test further along that ray's path thereafter, those systemsrequire the launching of a new ray originating at a point just beyondthe transparent primitive starting a new traversal from the root of theBVH hierarchy. Such a requirement to have the system launch a newtraversal each time a transparent primitive intersection is suspected,may incur a heavy performance penalty in terms of the speed with which aray tracing system produces its outputs. One of the advantages ofexample embodiments is that tests such as, for example, the alpha test(e.g., test whether the transparent primitive intersects the ray) aretreated as an extension of the ray intersection test, and as such onlybriefly interrupts traversal, rather than requiring the launch of a newray for each encountered alpha intersection.

Example embodiments provide for a variety of enhancements to the basicor default traversal of a BVH and shading in ray tracing and providemechanisms for instrumenting, augmenting, or overridinghardware-accelerated traversal of the BVH in a traversal coprocessor(e.g., TTU 700) with programmable capabilities running on a streamingmultiprocessor (e.g., SM 132).

The TTU 700 as described above performs accelerated tree traversal forray tracing. As described above, TTU 700 performs queries on behalf ofthreads running in SM 132, where, according to some example embodiments,each thread represents a respective ray. That is, in certain exampleembodiments, each thread determines the intersections of a respectiveray with the BVH. Taking one or more rays (e.g., typically, in someembodiments, a respective ray from each thread in a group of threadssuch as a warp) from the SM 132 as input, TTU 700 accelerates traversalof the BVH in order to return ray-primitive intersection information(e.g., triangles or other primitives that are intersected) to be used inthe shading processing that is subsequently performed by the SM 132 oranother component of the GPU. Example non-limiting embodiments providefor performing such accelerated traversal in a manner that enables finercontrol by the application(s) (e.g., TTU-accelerated ray-tracedrendering in a software application running on a GPU) for which the raytracing is performed. Each ray declares how it will handle differenttypes of primitives and nodes as a function of the mode bits andparameters specified with the ray and parameters specified within thenodes and primitives of the BVH.

Thus, example embodiments provide means for an application to fine-tuneTTU-accelerated traversal for purposes such as, but not limited to,limiting traversal to a portion of the acceleration data structure or toallow software running on the SM to interrupt traversal to override oraugment specific nodes or classes of nodes in the acceleration datastructure.

In order to facilitate the query-specific dynamic and programmablechange of the traversal process noted above, example embodiments providea per-ray set of ray operations (each ray operation is referred to as a“RayOp”), associated ray parameters, ray flags and mode flags, basedupon which the behavior of the TTU traversal can be changed on a per-rayand/or per-intersection basis. Some example embodiments extend the TreeTraversal Unit described in U.S. Pat. No. 9,582,607 (which isincorporated herein by reference in its entirety) to include, amongother things, a set of per-ray RayOp tests to be performed on theintersections, associated ray parameters, ray flags and mode flags, andextends the tree structure described in U.S. patent application Ser. No.14/697,480 (which is incorporated herein by reference in its entirety)to include, among other things, a per-child node parameter (referred toas the “real” parameter) for use in the RayOp tests. The RayOp tests arein addition to ray intersection tests that are performed duringtraversal. For example, in one non-limiting embodiment the RayOp testsare only performed on child nodes and primitives that have beenintersected by the ray. Whereas the ray intersection tests are based ongeometric aspects (e.g., location coordinates, direction, length, sizeetc.) of the ray and the BVH, at least some RayOp tests may not be basedupon geometric aspects of either the ray or the BVH.

The TTU performs a RayOp test for a ray by evaluating a predeterminedRayOp test expression using the ray's RayOp identifier (referred to inthis disclosure as the ray's RayOp opcode), ray parameters and the childnode's rval parameter at each potential traversal step. According to anembodiment, the RayOp specifies a per-ray test to be performed for eachchild of each node tested during traversal using two per-query RayOptest parameters A, B and rval which is specified for each child of anode. An example RayOp test provides for testing a left hand sidenumerical value based on a ray parameter with respect to a particulararithmetic or logic operation, against a right hand side value based ona ray parameter and a parameter (e.g., rval parameter) of theintersected node. As described below, other forms of RayOp tests may beused in various embodiments.

Depending on the result of the RayOp test and the ray's mode flags, theTTU may determine how it would handle different node types and primitivehit types encountered during traversal—such as, for example, whether thechild node should be traversed, ignored, or returned to the SM forspecial handling, or whether the primitive intersection should besuppressed, retained, or returned to the SM for special handling. Thedetermination may also be made so as to be consistent with one or moreray flags. The ray's ray flags may specify, for example, an order oftraversal for the bounding volumes (e.g., child bounding volumes),whether or not to pop a stack (e.g., a stack that represents the stateof the traversal) on return from traversal, whether or not to reportnode references to the SM when ray's tmin . . . tmax interval startsinside the node's bounding box, whether or not to return at the firsthit of an intersection, front-facing settings, and cull settings.

The mode flags specify the behavior of the TTU in how it should handlespecific node types and primitive test outcomes as a function of whetherthe RayOp test passes or fails. The specified mode flags may beconsidered in two categories: mode flags which affect the traversalstate passed to the stack management unit in response to the childbounding volumes intersected by the ray complet test (RCT) unit such asthe ray complet test block 710, and mode flags which affect traversalstate and passed to the stack management unit and values pushed to theresult queue by the intersection management unit (e.g., block 722) as aconsequence of primitives tested by the ray primitive test subunit(e.g., ray-triangle test block 720). The former may be referred to asRCT mode flags, and the latter may be referred to as RPT mode flags.

When the RCT unit 710 intersects a child bounding volume, the RCT unitperforms the RayOp test specified by the ray's RayOp query parametersusing the ray's A, B parameters and the complet child's rval parameter(and optionally, invert parameters). The RCT unit 710 performs theaction enumerated by the appropriate RCT mode flags based on the resultof the RayOp test (or the inverse of the result of the RayOp test, ifthe child node's invert flag is set). For example, if a ray withRayOp=EQUAL, A=0x0 and B=0xFF intersects a complet child node whose rvalis 0x1 and whose invert field was set to FALSE, the RayOp test (e.g.,0x0==0x1 & 0xFF) will fail. Based upon the result of the RayOp test, theappropriate mode flag(s) are identified. If, for example, the identifiedmode flag(s) (e.g., ch_f mode flag) indicate that the complet child isto be culled when they RayOp test fails, then the TL 712 may not push astack entry onto the ray's traversal stack for this complet child eventhough the ray intersected the complet child's bounding volume. In someembodiments, the RCT unit 710 performs the RayOp test, and passes theresult of the test to the TL subunit 712 which uses the test result tochoose between the available modes.

The mode flags described above are examples, and many more mode flagsand their respective configuration are described in relation to FIGS.10B and 10C and in relation to FIGS. 14-16.

In cases where the RayOp and mode flags indicate that the result is tobe returned to the streaming processor for special handling, the ray,its traversal state, and its result queue contents may be returned tothe SM in their entirety. The SM can perform additional processing asrequired (for example, interpolating texture coordinates and evaluatingan alpha texture to determine whether an alpha intersection is to beignored or not, etc.) or as specified, and if necessary, the SM mayresubmit the query with the same or altered query parameters (forexample, resubmit the query with a shortened ray) to the TTU.

In some embodiments, a mechanism is also provided to communicate theresult of the RayOp test performed in the RCT test block 710 to the RTTtest block 720 for subsequent use.

By providing a query structure and a BVH structure that can customizeeach ray's traversal and primitive intersection testing behavior in atraversal coprocessor such as, for example, TTU 700, applications canaffect dynamic changes in ray-tracing rendering, in at least some cases,without requiring regeneration, modification, or duplication of BVHdata. Changing the default behavior of the traversal may includechanging a state of the traversal (e.g., selecting a different portionof the BVH for traversal or a different order or traversal from thedefault configured behavior) or changing an output returned (e.g.,changing one or more of the intersections) returned to the SM.

The mechanism is described above in relation to FIGS. 10B and 10C, but abrief overview of the different types of nodes of a traversal tree thatmay be included within a BVH and encountered during traversal, as wellas the various hit types that the TTU 700 can return to the SM isprovided below.

The BVH, as described above, includes a hierarchically arranged (e.g.,in a tree structure) set of bounding volumes, with each volumeencompassing a three dimensional portion of a scene. Leaf nodes of theBVH tree may include ranges of geometric primitives (e.g., triangles),items, item ranges or instance nodes. As noted above, FIG. 8A shows anexample 3D scene recursively-subdivided into bounding volumes, and FIG.8B shows an example tree data structure that can represent the 3D scenein FIG. 8A.

The description here uses the terms “bounding volume hierarchy” (BVH)and “acceleration structure” interchangeably. Example embodiments aredescribed primarily as using a BVH as the acceleration structure.However, persons of skill in the art will understand that certainexample embodiments may include acceleration structures other than thetype of BVH structures described in this disclosure.

In some example embodiments, the BVH is stored in one or more completsthat are a compressed format for storing sets of nodes of the BVH in atree structure. Each complet, as noted above, specifies a root, interiornodes and leaf nodes, with each node representing a respective boundingvolume of the BVH. The nodes of each complet may be stored in contiguousmemory.

During the traversal operation, the BVH is retrieved from memory towhich it is written by application software to the TTU in complets. Forefficient retrieval, the size of the complets may be configured tocorrespond to the cache and/or other memory access capabilities of thehardware. For example, in some embodiments, each complet is 128Bcorresponding to the size of a cacheline. Since, as noted above, eachcomplet includes a root node and child nodes, the stored BVH can beconsidered a tree of complets. For efficient traversal, child completsof a parent complet are preferably stored contiguously in memory, withpointers to the child complets being stored in the parent complet. Thepointers may be stored in compressed form.

The complets of the BVH themselves being arranged in a tree structure,example child node types of a complet include complets, instance nodes,items or item ranges and primitives or primitive ranges.

When a child complet is encountered during traversal, the defaultbehavior according to some configurations is for the TTU 700 to continuetraversal by retrieving the child complet from memory and descendinginto the child complet to traverse the nodes of the child complet. Thedefault behavior can also differ according to the node type of thecomplet child.

An instance node child of a complet may include one or more pointers tothe hierarchy of nodes of the BVH, or more specifically to anothercomplet, that is in a different coordinate space than the instance nodeand the complet that includes the instance node as a child node, and atransformation for transforming a ray from a world or other coordinatespace to the coordinate space of the referenced complet. A BVH mayinclude zero or more instance nodes, each of which provides a connectionfrom a leaf node of one complet to the root of another. When a BVH isconsidered as comprising two or more smaller BVHs, an instance node maybe considered to provide a connection from a first BVH in a firstcoordinate system to a second BVH, which is arranged as a child of thefirst BVH, that is in a second coordinate system. According to someembodiments, the instance node structure may contain, in addition to theone or more pointers to the referenced-complet or BVH, flags that can beused to affect behavior (e.g., back-face culling behavior) in thereferenced-complet or BVH, and a transformation matrix (in homogeneouscoordinates) from the coordinate system of the referencing-complet orBVH to that of the referenced-complet or BVH. The transformation may befrom the world space to the object space of the referenced-complet orBVH, or from a first object space of the referencing-complet or BVH to asecond object space of the referenced-complet or BVH. The localcoordinate system of the object space of the referenced-complet or BVHmay be defined as a translation applied to the coordinate system of thespace (e.g., world space or another object space) of thereferencing-complet or BVH. According to some embodiments, in additionto translating the origin of the global or other local coordinate systemof the referencing-complet or BVH to a new origin of the localcoordinate system, a rotation and/or scaling transformation may beapplied to the global or other local coordinate system in order todefine the local coordinate system of the referenced-complet or BVH.

An item range child of a complet specifies a group of one or moreprimitives of a type that is not tested for intersection by the TTU.According to some embodiments, the TTU delegates the intersectiontesting of an item range to software running on the SM. For example,when an item range, consisting of an index (e.g., which may be derivedfrom a user or software-provided “item range base” stored in thecomplet) and a e.g., 6-bit count of items, is encountered duringtraversal, by default, item ranges are returned to SM 132 as an“ItemRange” hit type, consisting of for example an index (e.g., 47 bitindex), count (e.g., 6 bit count), and the t-value (e.g., coordinatesalong the ray) of the intersection with the leaf bounding volume.

A primitive range (in one embodiment, a triangle range) of a completspecifies a group of one or more compressed or uncompressed alpha (e.g.,transparent) or opaque primitives of the primitive type that the TTU canperform intersection tests for some or all types of query handled by theTTU stored in an array of contiguous blocks. Zero or more primitivebuffers containing primitives stored as e.g., a triplet or other set ofe.g., fp32 coordinates or parameters per vertex or in a losslesscompressed format readable by the TTU 700. The primitive rangeparameters may include non-vertex parameters (e.g. radius). In addition,an alpha bit may be provided per primitive, indicating primitives that auser or software has determined as requiring special handling bysoftware to determine whether the primitive is actually intersected by aparticular ray. Primitive buffers may, in certain example embodiments,be organized into blocks that are memory and/or cache aligned, forexample, 128B in size and 128B-aligned. In one embodiment, a trianglerange specifies a group of one or more compressed or uncompressed alpha(e.g. transparent) or opaque triangles that the TTU can test forintersections against rays.

In one embodiment, when a triangle range, corresponding to a contiguousset of triangles within a triangle buffer, is encountered duringtraversal, by default in certain example embodiments, the triangle rangeencountered by a ray is handled natively by the TTU 700 by testing thetriangles in the range for intersection and shortening the rayaccordingly. If traversal completes and a triangle was intersected, thedefault behavior is for the triangle ID to be returned to SM 132, alongwith the t-value and barycentric coordinates of the intersection. Thismay be referred to as the “Triangle” hit type. In some embodiments, bydefault, intersected triangles with the alpha bit set are returned to SM132 even if traversal has not completed. As described in more detailbelow, a traversal stack returned to the SM with the intersection maycontain the state required to continue traversal if software determinesthat the triangle was actually transparent. Triangle intersection insome embodiments is not supported for beams, so encountered triangleranges may, by default, be returned to SM 132 as a “TriRange” hit type,which includes a pointer to the first triangle block overlapping therange, parameters specifying the range, and the t-value (e.g. parametricdistance(s) of the intersection) of the intersection with the leafbounding volume.

Each ray presented for querying by the streaming processor (e.g., SM132) to the tree traversal unit (e.g., TTU 700) includes: (1) raygeometric parameters such as, for example, the ray's position, directionvector, and the near and far parametric interval (tmin, tmax); (2)traversal state which may include a stack of one or more stack entrieswhich reference blocks in the BVH tree structure which are to be fetchedand tested against the ray for intersections; and (3) mode flags whichdescribe how the ray is to handle specific types of interactions duringtraversal and RayOp information.

For each ray, the ray's geometric information such as, for example, theray's origin, direction, and the near and far parametric interval, maybe provided. The origin, direction, and the start and the end of theparametric interval may each be specified as coordinate tuples. The nearand far parametric positions are referred to herein as tmin and tmax,respectively, and may be thought of as representing the segment ofcurrent interest along the ray. In some embodiments, a beam may bespecified in the query. A beam is additionally specified by a secondorigin and direction.

An example query or ray data structure 1102 is shown in FIG. 11A. Insome example embodiments, the ray information is communicated to the TTUby way of registers in the SM. In example embodiments in which ray datais passed to the TTU via memory, data structure 1102, or part thereof,may reside in a memory to be read by the TTU. Ray data structure 1102may include a ray identifier 1104 which may be assigned by the TTU orthe SM to uniquely identify rays that are concurrently being processedin the TTU, ray origin 1106, ray direction 1108, ray start (tmin) 1110and end (tmax) 1112 parameters. According to some embodiments, the rayinformation 1102 may also include ray flags 1114, RCT mode flags 1116(also referred to as RCT mode bits), RPT mode flags 1118 (also referredto as RPT mode bits) and one or more ray operation (RayOps)specifications. Each RayOps specification may include a ray operationopcode 1120 and ray test parameters (e.g., ray parameters A & B) 1121.These ray data attributes are described below.

As will be described below, a “RayOp” test is performed for eachprimitive or child bounding box intersected by a ray using the ray'sRayOp opcode, mode bits, and parameters A and B as well as one or moreparameters (e.g., ChildType, “rval” parameter or “alpha” flag) specifiedwith each intersected complet child or primitive. In exampleembodiments, the ChildType and rval parameters used in RayOp testsdescribed below are specified for each child in a complet, or for thecomplet as a whole, and the RayOp opcode, mode bits, and parameters Aand B are specified for each ray. An example of a data structure 1122may hold RayOp-related information or a complet or bounding volumeaccording to some embodiments is shown in FIG. 11B. According to someembodiments, data structure 1122 may be stored in a memory by software,and the TTU may either access the data structure in the memory and/ormay receive the data structure into the TTU internal memory. The datastructure 1122 may include header information 1124, one or more overrideflags 1126 and an rval 1128. Header information may include geometricinformation, node type information etc., related to the node. Overrideflags 1226 and rval parameter 1128 are described below.

During traversal of a BVH by a ray in the TTU, the traversal state forthe ray is maintained in the TTU. The traversal state may include astack of one or more entries which reference bounding volumes and/orcomplets in the tree structure which are to be fetched and testedagainst the ray. A traversal stack 1202 according to some embodiments isshown in FIG. 12. The traversal stack 1202 may include any number ofstack entries. In some embodiments, the stack 1202 is limited to a smallnumber of entries (e.g., a “short stack” of 4 entries) so that theexchange of the stack between the TTU and SM can be made more efficient.In FIG. 12, a bottom stack entry 1204 and a top stack entry 1206 areshown with one or more entries in between.

TTU 700, in at least some embodiments, is stateless. That is, noarchitectural state is maintained in the TTU between queries. Thetraversal stack enables the TTU to maintain state during a query, andpass that state to the SM as required. The software running on the SMcan request continuation of a previous query by passing back to the TTUthe state as contained in the traversal stack. The SM conveys traversalstate for each query to the TTU using one or more stacks or other datastructures of a specific size StackLimit (SL), and the TTU returnstraversal state back to the SM using one or more stacks or other datastructures of size SL. Within the TTU, each ray maintains one or morestacks or other data structures which may be of size>=SL.

FIG. 13 shows an example results queue according to some embodiments. Aresult queue, as described elsewhere, is used for the TTU to transmitinformation about the intersections detected so far to the SM. In someembodiments, the result queue 1310 is small and may only accommodate anopaque primitive intersection result 1312 and/or one or more alphaprimitive intersection result 1314. However, in other embodiments, theresult queue may accommodate more entries representing detectedintersections.

The diagrams of FIGS. 10B and 10C above summarize the ray-tracingpipeline and shows the data flow and interaction between components fora representative use case: tracing rays against a scene containingprimitives such as triangles, with instance transformations and certainintersection tests being handled in hardware. As described in relationto FIG. 10B, one or more rays can be presented to the TTU at a time forquerying by the SM, and each ray presented to the TTU for traversal mayinclude the ray's geometric parameters, traversal state, and the ray'sray flags, mode flags and RayOp information. The traversal operations ofFIGS. 10B and 10C may use a ray data structure such as that shown inFIG. 11A, a node data structure such as that shown in FIG. 11B, one ormore traversal stacks such as that shown in FIG. 12 and a result queuesuch as that shown in FIG. 13. A result queue can in some embodiments bea single entry that holds an opaque or an alpha result.

The mode flags enable traversal behavior to be changed by e.g.,specifying an auxiliary arithmetic or logical test in the form of aRayOp to suppress, override, or allow storage of an intersectionencountered during a traversal such as that shown in FIG. 10B. As notedin relation to FIG. 10B, this capability can be used by applications todynamically and/or selectively enable/disable sets of objects forintersection testing versus specific sets or groups of queries, forexample, to allow for different versions of models to be used when gamestate changes (for example, when doors open or close) or to providedifferent versions of a model which are selected as a function of thelength of the ray to realize a form of geometric level of detail, or toallow specific sets of objects from certain classes of rays to make somelayers visible or invisible in specific views. This capability alsoallows changing alpha to opaque and vice versa. The mode flags mayenable traversal behavior to be changed in accordance with such aspectsas, for example, a depth (or distance) associated with each boundingvolume and/or primitive, size of a bounding volume or primitive inrelation to a distance from the origin or the ray, particular instancesof an object, etc.

The set of mode flags presented with each query (e.g., ray) may at leastpartly control how the TTU will process the query when the queryintersects the bounding volume of a specific type or intersects aprimitive of a specific primitive type. In addition to the set of modeflags which may be specified separately for the ray-complet intersectionand for ray-primitive intersections, the ray data structure may specifyother RayOp test related parameters, such as the ray flags, rayparameters and the RayOp test. The TTU reserves a “ray slot” for eachactive ray being processed in the TTU, and may store the ray flags, modeflags and/or the RayOp information in the corresponding ray slot bufferwithin the TTU during traversal.

The ray flags can be used by the TTU to control various aspects oftraversal behavior, back-face culling, and handling of the various childnode types, subject to a pass/fail status of an optional RayOp test.RayOp tests, therefore, add flexibility to the capabilities of the TTU,at the expense of some complexity.

FIG. 14 shows a flowchart of a process 1400 that may be performed when aray-bounding volume intersection is detected during ray tracing pipelineprocessing. For example, process 1400 may be performed when aray-bounding volume intersection is detected in step 1010 and/or 1024shown in FIG. 10B (e.g., in the top level traversal and/or in the bottomlevel traversal) with respect to process shown in FIG. 10B. Ray-boundingvolume intersection tests 1010 and/or 1024 may be performed in TTU 700in the ray-complet test block 710.

The intersection detection at step 1402 may occur when testing aretrieved complet, or more specifically, testing a child bounding volumeincluded in the retrieved complet. According to example embodiments,when a complet is processed, the TTU may optionally perform the RayOptest on each child. In some embodiments, the RayOp test is run only onthe children whose corresponding bounding volume was intersected by theray.

Thus at step 1404, it is determined that the fetched complet has atleast one child, and at step 1406 the child bounding volumes areaccessed and tested in parallel. In some embodiments, each retrievedcomplet has zero or one parent complet and zero or more complet childrenand zero or more leaf node children. In some embodiments, each fetchedcomplet references its parent complet with a parent pointer or offset,encodes child pointers in compressed form, and provides a per-childstruct containing a child bounding box and per-child data used by theRayOp test (e.g. Rval, invert RayOp result flag), and (in the case ofleaf nodes) data used to address and process blocks of leaf nodes (e.g.item count, starting primitive index, number of blocks in leaf, a flagindicating the presence of alpha primitives). In some embodiments,processing steps 1408-1414 may be performed in parallel for all childrenbounding volumes. In yet other embodiments, processing steps 1408-1414may be performed child-by-child, in parallel for groups of childbounding volumes. etc.

Each of the child bounding volumes of the intersected parent arepotential traversal targets. In example embodiments, an instance node isa leaf node that points to the root node of another BVH. The RayOp testmay be performed on the child nodes of an intersected parent based uponthe child bounding volume information available in the already retrievedcomplet, before determining whether or not to retrieve the completscorresponding to the respective child nodes for traversal.

At step 1408, the RayOp test specified for the ray is performed withrespect to the accessed child bounding volume. As noted above inrelation to FIG. 11A, the RayOp opcode may be specified as part of theray data provided to the TTU 700 from the SM 132. In exampleembodiments, when the ray-bounding volume intersection is detected atray-complet test block 710, the traversal logic block 712 may performthe RayOp test based on the ray and the intersected bounding volume'schild nodes. More specifically, the RayOp test specified by theparticular RayOp opcode specified for the ray is performed using theray's RayOp A, B parameters and the RayOp rval parameter specified forthe child bounding volume. In some embodiments, the RayOp test isperformed only for child bounding volumes that are themselves found tointersect the ray. For example, when the RCT unit tests a ray against acomplet, each of the complet's child bounding volumes are also testedfor intersection with the ray and, for each child that is found tointersect the ray, the RayOp test is performed.

An example RayOp test may provide for testing a left hand side numericalvalue based on a ray parameter with respect to a particular arithmeticor logic operation, against a right hand side value based on a rayparameter and a parameter of the intersected node. The RayOp test may bean arithmetic or a logical computation that results in a true/falseoutput. The particular computation (e.g., the particular relationshipbetween the RayOp A and B parameters, the RayOp opcode and the rvalparameter) may be configurable, and/or may be preprogrammed in hardware.In some embodiments, each ray may specify one of a plurality of opcodescorresponding to respective RayOp tests. Thus, the RayOp test provides ahighly flexible technique by which rays can change the default raytracing behavior of the TTU 700 on an individual or group basis.

The RayOp tests may include any of, but are not limited to, thearithmetic and/or logic operations ALWAYS, NEVER, EQUAL, NOTEQUAL, LESS,LEQUAL, GREATER, GEQUAL, TMIN_LESS, TMIN_GEQUAL, TMAX_LESS, TMAX_GEQUAL,as opcodes. The opcode specified in a ray may, in some embodiments, beany logical or arithmetic operation.

For example, if the ray's RayOp opcode is defined in the ray informationprovided to the TTU as “EQUAL”, and the RayOp A and B parameters are 0x0and 0xFF, respectively, and the accessed child bounding volume's RayOprval is 0x1, the RayOp test may be “A EQUAL rval && B”. Thus, with theabove noted values for the various parameters and opcode, the RayOp testyields “0x00==0x1 && 0xFF”. Thus, (since this is false) the RayOp testin this example must return false. That is, in this particular example,the RayOp test fails for the ray and the accessed child bounding volume.

In some embodiments, the child bounding volume may also have an invert(“e.g., inv”) parameter associated with the RayOp testing. If the rayalso has an invert parameter associated with the RayOp, and the invertparameter is set to TRUE (e.g., 1), then the returned RayOp result maybe the inverse of the actual RayOp test result. For example, if theray's invert parameter was set to TRUE, then the RayOp test in the aboveexample would return TRUE. RayOps may be comparable to the Stencil Testin raster graphics, except that Stencil Test has the ability to allow afragment write to occur even when the fragment failed the Depth Test. Inexample embodiments, the RayOps do not have the capability to convert amissed complet child into a hit complet child, but in other embodimentsthe TTU could allow programmability so a RayOp could treat a miss as ifit were a hit.

It is not necessary that the RayOp test has the parameters and theopcode arranged in a relationship such as “A EQUAL rval && B”. Exampleembodiments may have the parameters and the opcode arranged in anylogical or arithmetic relationship. In some embodiments, for example,the relationship may be of a form such as “TMIN_LESS rval” or “TMIN_LESSA & rval”, expressing a relationship between a specified area ofinterest and either the node parameter alone or a combination of the rayparameters and the node parameter. The example opcodes TMIN_LESS, TMIN_GEQUAL, TMAX_LESS, TMAX_GEQUAL all enable the RayOp test to be basedupon the intersection's start or end (e.g., TMIN and TMAX in the aboveopcodes may represent the t values at the ray's entry to and exit fromthe intersected volume (e.g., bbox.tmin, bbox.tmax below),respectively), and to include aspects of either the tested node alone orthe tested node and the ray parameters A and/or B. For example, whenrval is encoded with a distance value for the node, “TMIN_ LESS rval”may represent a test such as “is the tested node at a distance less thanthe beginning of the area of interest?”. Opcodes based on aspects of theray other than start/end of the ray are also possible, and may be usedfor the RayOp in other embodiments. In contrast to opcodes that encodean aspect of the ray's geometric properties, example opcodes ALWAYS,NEVER, EQUAL, NOTEQUAL, LESS, LEQUAL, GREATER, GEQUAL enable anarbitrarily-specified left hand side value to be compared to anarbitrarily-specified right hand side value. Thus, example opcodesALWAYS, NEVER, EQUAL, NOTEQUAL, LESS, LEQUAL, GREATER, GEQUAL may beused for RayOp tests that depend on some geometric aspects of either theray or the tested node, and moreover may be used for RayOp tests thatare independent of any geometric properties of either or both the rayand the tested node. Thus, in example non-limiting embodiments,“FLT_TMIN_LESS”, “FLT_TMIN_GEQUAL” and “FLT_TMAX_LESS”, and“FLT_TMAX_GEQUAL” RayOp tests actually evaluate the expressionsbbox.tmin<A*rval+B, bbox tmin>=A*rval+B, bbox.tmax<A*rval+B,bbox.tmax>=A*rval+B, respectively. In one particular non-limitingembodiment, rval is an FP0.6.2 value and A and B are FP1.5.10 values forthese operations. Moreover, in some non-limiting example embodiments,since the FLT_TMIN and FLT_TMAX tests operate on the bounding box tminand bounding box tmax values which may be geometric values computed inthe intersection test, these RayOps may be used for geometriclevel-of-detail (e.g., where A corresponds to the cosine of the angle ofthe cone subtends the image plane pixel and B corresponds to theaccumulated length of the previous bounces of the ray and rvalcorresponds to the max length of the bounding box). In some embodiments,the opcodes (e.g., FLT_TMIN_LESS, FLT_TMAX_LESS) provides for comparinga value computed during the ray/acceleration data structure intersectiontest scaled by one geometric attribute associated with the ray andbiased by another geometric attribute associated with the ray to atleast one geometric parameter associated with the at least one node.

At step 1410, one or more mode flags corresponding to the RayOp testresult are identified. Each mode flag may be specified, for example, ina predetermined bit position in a ray data structure, and may includeany number of bits. Each mode flag maps a result of the RayOp test or acombination of the result of the RayOp test and a node type of thetested node, to a particular action to be taken by the TTU. In someembodiments, the mode flags are separately specified with the ray forray-complet testing and ray-primitive testing respectively. Thus, inresponse to completing the RayOp test at step 1410, the applicable modeflag(s) may be found in the RCT mode flags specified for the ray.

In the above example, since the RayOp test failed, the applicable modeflag(s) include the “ch_f mode flag”. As described above, “ch_f”represents that the RayOp test failed for intersected child of typecomplet.

At step 1412, an action to be performed based on the identified modeflag(s) and/or ray flags is identified, and at step 1414, the action isperformed.

RCT mode flags express for each complet child type (e.g., complets,instance leaf nodes, item range leaf nodes, primitive range leaf nodes)how the TTU is to handle ray intersections with child-bounding-volumesfor child nodes of that type for those rays that pass or fail the RayOptest. Example RCT mode flags include “In_f”, “In_p”, “Ir_f”, “Ir_p”,“pr_f”, “pr_p”, “ch_f”, and “ch_p”.

The mode flag “In_f” (“modeInstanceNodeFail”) specifies an action to beperformed when the RayOp test fails for intersected child of typeinstance node (“InstanceNode”). The supported actions may includeprocessing in TTU, culling (e.g., suppress push of instance node ontotraversal stack), return as node reference, or return to SM.

The mode flag “In_p” (“modeItemRangePass”) specifies an action to beperformed upon the RayOp test passing for an intersected child of typeinstance node. The supported actions may include processing in TTU,culling (e.g., suppress push of instance node onto traversal stack),return as node reference, or return to SM.

The mode flag “Ir_f” (“modeItemRangeFail”) specifies an action to beperformed upon the RayOp test failing for an intersected child of typeitem range (“ItemRange”). The supported actions may include returning toSM (e.g., push item range hit into the result queue), culling (e.g.,suppress storage of item range hit in the result queue), or return asnode reference.

The mode flag “Ir_p” (“modeItemRangePass”) specifies an action to beperformed upon the RayOp test passing for an intersected child of typeitem range. The supported actions may include return to SM (e.g., pushitem range hit into the result queue), cull (e.g., suppress storage ofitem range hit in the result queue), or return as node reference.

The mode flag “pr_f” (“modePrimitiveRangeFail”) specifies an action tobe performed upon the RayOp test failing for an intersected child oftype primitive range (“PrimitiveRange”). The supported actions mayinclude processing in TTU (e.g., push entry onto traversal stack), cull(e.g., suppress push of triangle range stack entry onto traversalstack), return as node reference, or return to SM.

The mode flag “pr_p” (“modePrimitiveRangePass”) specifies an action tobe performed upon the RayOp test passing for intersected child of typeprimitive range. The supported actions may include processing in TTU(e.g., push entry onto traversal stack), cull (e.g., suppress push ofprimitive range stack entry onto traversal stack), return as nodereference, or return to SM.

The mode flag “ch_f” (“modeCompletFail”) specifies an action to beperformed when the RayOp test fails for an intersected child of typecomplet (“complet”). The supported actions may include traversing inTTU, cull, or return as node reference.

The mode flag “ch_p” (“modeCompletPass”) specify an action to beperformed when the RayOp test passes for an intersected child of typecomplet. The supported actions may include traversing in TTU, cull, orreturn as node reference.

In some embodiments, in addition to the mode flag(s) selected inaccordance with the RayOp test result, the selected action may beperformed in a mariner consistent with one or more ray flags specifiedin the ray data. The ray flags, such as ray flags 1214, may specifybehavior independent of any particular intersection.

In example embodiments, the ray flags may specify an order of traversalfor the bounding volumes, whether or not to pop the stack on return,whether or not to report node references to the SM when the ray's tmintmax interval starts inside the node's bounding box, whether or not toreturn at the first hit of an intersection, front-facing settings, cullsettings and the like.

The ray flags for traversal order may specify any one of: traversal inorder of parametric distance along the ray, traversal in memory order ofthe bounding volumes and/or primitives, decreasing x coordinate,increasing x coordinate, decreasing y coordinate, increasing ycoordinate, decreasing z coordinate, and increasing z coordinate, etc.More specifically, the traversal order dictates the order that stackentries get pushed onto the traversal stack when complet child boundingvolumes are intersected by the ray. In particular, when a node isintersected, the traversal order specified by the ray flags may be usedby the TTU to determine in which order the child nodes of theintersected node are to be pushed into the traversal stack. It is usefulfor example for tracing shadow rays that are set to return on the firsthit found and not specifically the nearest hit, where it is desirablefor such rays to first test against larger primitives (and thus morelikely to be hit). If the BVH is built in such a manner that the memoryorder of leaf node children is largest-first, then it is desirable tochoose memory order over t-order for such rays because it is more likelyto return quicker to the SM and t-ordering is immaterial for such rays.

One may desired to change traversal order (t-order) for any of severalreasons. For example, when trying to find the closest triangle, onewould typically want to use—order so that those primitives that mightcome earlier in parametric length are tested first. If those primitivesare intersected, then primitives and complets farther along the ray maynot need to be tested. When trying to find any intersection (e.g., totest if a point is in shadow from a light), then one may not care aboutwhich specific primitives are intersected and may want to test theprimitives that are most likely to be intersected first. In that case,the BVH builder may put the largest triangles earlier in the tree suchthat memory order will find them first.

The x/y/z ordering of traversal each may be used to approximatet-ordering in the case when t-ordering may not be consistent.Specifically, the t-intersection for a beam traversal and a raytraversal may not be consistent because the queries are differentshapes. (e.g., they may be similar, but not identical). The x/y/zordering, however, are each based on the bounding volume positionsalone, and are consistent. If the processing requires something likesharing the stack between a beam and a ray, then one may use theconsistent x/y/z ordering to get performance close to t-order.

The ray flags for indicating whether to pop the traversal stack onreturn (e.g., “noPopOnReturn”), may specify whether the stack is to bepopped, and/or whether to return the result of the traversal withoutpopping the stack. Returning the result of the traversal without poppingthe traversal stack may enable the SM to rerun the same traversal ormodify the stack before starting a new traversal.

The ray flags controlling the reporting of hits (e.g., “reportOnEnter”flag) may specify that the TTU is to only report a child hit if AABBintersection point t is greater than or equal to the ray's tmin, and tocull (and/or not report to the SM) otherwise. This flag enables abounding volume to not be reported to the SM even if it is intersected,if that intersection point (upon the ray's entry to the bounding volume)occurs before the ray's specified area of interest. One example use ofthis flag is for ray marching where after finding an intersection, thetmin is advanced to be the start of that intersection. On relaunch onemay want to find the next intersection, but typically would not want toreport again the intersection that was just returned. By setting thereportOnEnter flag, returning the intersection again to the SM can beavoided because a relaunched ray does not enter the volume, but ratherstarts inside of it.

The ray flags controlling whether to terminate upon the first hit (e.g.,“terminateOnHit”) specifies whether the TTU is to return at the firsthit for the ray found during traversal, or to keep on traversing untilit can return the parametrically nearest hit found.

The ray flags(s) that indicate what triangles are to be considered frontfacing (e.g., “facingfrontFaceCW”) may be used to specify certaintreatment of intersected leafs. For example, these flags may specifytreatment of counterclockwise winding triangles as front facing, ortreatment of clockwise winding triangles as front facing assumingright-handed coordinate system.

Ray flags controlling culling of intersected primitives (e.g.“cullMode”) may be specified to indicate no culling, cull back-facingprimitives, cull front facing primitives, or to disable culling andprimitive edge testing.

The traversal logic (e.g., traversal logic block 712) performs theaction enumerated by the appropriate mode flag(s) based on the result ofthe RayOp test (or the inverse of the result of the RayOp test, if thechild invert flag is set). In the above example, since the ch_f modeflag indicates that the child bounding volume is to be culled when theyRayOp test fails, then the traversal logic will not push a stack entryonto the ray's traversal stack for this child bounding volume eventhough the ray may intersect the child's bounding volume and the defaultbehavior for intersected child bounding volumes is for the child to bepushed into the traversal stack. Note that ray could have, instead ofspecifying a value for ch_f mode flag indicating that the child is to beculled if the RayOp test fails, indicated alternatively that the childis to be traversed in the TTU, or be returned as a node reference.

The action by the traversal logic may be performed in a mannerconsistent with ray flags of the ray. For example, where the ray flagsindicate a particular traversal order, the child bounding volumesselected for traversal in accordance with the RayOp test may be pushedto the traversal stack in a manner consistent with the traversal orderspecified by the corresponding ray flag(s).

Steps 1404-1414 may be repeated for each child of the intersectedbounding volume. When each of the child nodes, or at least each of thechild nodes that are themselves found to intersect with the ray have hada RayOp performed, the parent bounding volume has completed itstraversal step. That is, in the case where a complet includes only aroot bounding volume and its child bounding volumes, the traversal ofthat complet has completed. More generally, as when the complet includesa root and more than one level of nodes, the traversal of the complet iscomplete when all the leaf nodes of the complet, or at least all thosethat have not been culled, have been subjected to the ray-boundingvolume intersection test and/or the RayOp test.

FIG. 15 shows a flowchart of a process 1500 that may be performed at,for example, step 1414 in process 1400 when an intersected boundingvolume is a leaf

At step 1502, information regarding the ray-bounding volume intersectiondetection is received. The next step may be determined based on the typeof scene geometry contained in the intersected leaf bounding volume.Instance nodes, item ranges, and primitive ranges are processed in steps1504, 1508 and 1512, respectively.

If the scene geometry in the intersected bounding volume includes aninstance node, at step 1504 ray-instance node intersection detection isperformed. If the ray is determined to intersect the instance node, anentry is pushed to the traversal stack with the following information:an address of the instance node which specifies a transformation fromthe current (e.g., world) coordinate space to a different coordinatespace and a pointer to the root of another BVH in another (e.g., object)coordinate space, a “returnToSM” flag indicating whether to return thequery to the SM so that the SM can save off the traversal state of thequery in the current BVH and apply the transformation, and an“initialized” flag indicating whether the ray (or another instance ofthe ray cloned from the world space ray) has already been initialized.

If the scene geometry in the intersected bounding volume includes anitem range, at step 1506, ray-item range intersection detection isperformed. Based on the intersection detection, an entry is pushed on tothe traversal stack with the following information: a start addressspecifying the starting address of the item range data, and a countindicating the number of items in the range.

If the scene geometry in the intersected bounding volume includes aprimitive range, at step 1512 ray-primitive range intersection detectionis performed. At step 1514, it is determined whether to process theprimitives/primitive range in the TTU, or to push an entry into thetraversal stack with the following information: the address of the lastblock in the primitive range (“addrLast”), the index of the firstprimitive of the primitive range in the first cacheline (“triIdx”), theindex of the last primitive in the last cacheline in the range, or zeroindicating that the range ended in the last cacheline (“triEnd”), numberof blocks that contain the primitive range (“lines”), a “co flag”indicating whether or not opaque primitives are to be culled, a “caflag” indicating whether or not alpha primitives are to be culled, and a“rp flag” indicating whether or not the primitive range RayOp test waspassed.

In cases where the RayOp and mode flags indicate that the result is tobe returned to the streaming processor for special handling, the ray,its traversal state, and its result queue contents are returned to thestreaming processor in their entirety. The streaming processor canperform whatever additional processing that may be required (forexample, interpolating texture coordinates and evaluating an alphatexture to determine whether an alpha intersection is to be ignored ornot) and if necessary, the streaming processor can resubmit the querywith the same or altered query parameters (for example, the ray may beshortened when resubmitted by pulling tmax closer).

FIG. 16 shows a flowchart of a process 1600 that may be performed when,for example, in the operation of step 1502, a ray-bounding volumeintersection 1602 is detected with respect to a leaf bounding volumethat includes a primitive range (e.g., a triangle range) that can beresolved in the TTU.

At step 1604, the RayOp test for the ray is performed with respect tothe bounding volume. When the RCT unit 710 intersects a child boundingvolume which references a primitive range the TL subunit 712 performsthe RayOp test specified by the ray's RayOp query parameters using theray's A, B parameters and the complet child's rval parameter and storesthe result of the RayOp test in the rp flag stored in the stack entrycorresponding to the primitive range that gets pushed onto the top ofthe traversal stack, as described in relation to operation 1518 above.

When the stack management unit 740 pops that entry off the top of thestack and sends an activation to the primitive scheduler, the rp flag isforwarded by the primitive scheduler on to the RPT unit 720 along withthat activation. When the RPT 720 detects an opaque intersection oralpha intersection the RPT 720 retrieves the mode flag(s) correspondingto the type of primitive hit and the rp flag and applies the appropriateaction to handle the intersection. For example, if a ray with rpflag=TRUE intersects an opaque primitive, and the ray's “op_p” flagindicates that opaque primitive hits from passing RayOp tests are to beculled, then the RPT 720 will not push the opaque intersection to theresult queue.

At step 1606, the result of the RayOp test is stored in the rp flag, andan entry including the rp flag is pushed on to the traversal stack.

At step 1608, the stack is popped and the rp flag is provided to theray-primitive test block (e.g., ray/triangle test 1026 in FIG. 10B).

When the stack management unit pops that entry off the top of the stackand sends an activation to the primitive scheduler, the rp flag isforwarded by the primitive scheduler on to the RPT unit along with thatactivation.

At step 1610, in the ray-primitive testing, detect intersection betweenthe ray and the primitive. When the RPT detects an opaque intersectionor alpha intersection the RPT retrieves the mode flag(s) correspondingto the type of primitive hit and the rp flag and applies the appropriateaction to handle the intersection.

RPT mode flags specify TTU behavior as a result of completedray-primitive testing. Example RPT mode flag “at_f” (“modeAlphaFail”)specify actions to be performed upon the RayOp test failing for anintersected alpha primitive. The supported actions may include pushingalpha hits to a result queue (e.g., result 1310) to be communicated toSM, cull alpha hit (suppress alpha primitive test), or push alpha hit tothe result queue as an opaque hit. Another example RPT mode flagsinclude mode flag “at_p” (“modeAlphaPass”) which specify actions to beperformed when the RayOp test passes for an intersected alpha primitive.The supported actions may include pushing the alpha primitive hit toresult queue, culling alpha hit, and pushing alpha hit to the resultqueue as an opaque hit.

The mode flag “ot_f” (“modeOpaqueFail”) specify an action to beperformed when the RayOp test fails for an intersected opaque primitive.The supported actions may include pushing an opaque hit to the resultqueue, culling opaque hit, and pushing opaque hit to result queue as analpha hit. The mode flag “op_p” (“modeAlphaPass”) specify an action tobe performed when the RayOp test passes for an intersected opaqueprimitive. Supported actions may include pushing opaque hit to resultqueue, culling an opaque hit, and pushing an opaque hit to result queueas an alpha hit.

Some nodes or leafs (e.g. instance nodes, primitive ranges) may alsoinclude flags which interact with and/or override the RayOp test andmode flags. For example, the instance node header has flags “foa” (forceopaque to alpha), “fao” (force alpha to opaque), and “fnc” (force nocull) may override the values of mode flags “op_p”, “op_f”, “ap_f”,“ap_p” of an object space ray to override the values copied from itscorresponding world space ray. In example embodiments, the ray mode bitsfor lower-bvh traversal are copied from the upper-bvh ray mode bits.

At step 1612, the action is selected based on the rp flag and the rayprimitive mode flags. For example, if a ray with rp flag=TRUE intersectsan opaque primitive, and the ray's “op_p” flags indicate that opaqueprimitive hits from passing RayOp tests are to be culled, then the RPTwill not push the opaque intersection to the result queue. The selectionof the action may also consider any override parameters specified in thetested primitive(s) and/or other ray flags.

As described above, example embodiments provide a capability toprogrammatically change the default behavior of the traversal of anacceleration structure by a query. In some example embodiments, thesecapabilities are enabled within the chip-area constraints and otherhardware constraints imposed upon hardware acceleration of thetraversal. The capabilities enabled by embodiments provide, among otheraspects, for an applications to selectively process geometric primitivesof an object at certain depth levels for ray tracing, to select amongmultiple versions of an object in the BVH during ray tracing,selectively treat geometric primitives of objects based on level ofgeometric detail, selectively treat geometric primitives of objectsbased on level of resolution, selectively treat geometric primitives ofobjects based on type of material, selectively treat geometricprimitives of objects based on how far along the ray they areintersected, etc. Example embodiments may also enable on a per-ray basisto perform operations such as, for example, back face culling, whichprovides for ignoring all primitives that are pointed away from theorigin of the particular ray, and front face culling, which provides forignoring all primitives that are pointed toward the origin of theparticular ray. Moreover, some example embodiments, also provide foroverriding per-ray behavior for particular intersections: for example,some nodes of the BVH, such as instance nodes, may have override flagsthat can override a per-ray behavior such as back face culling on aninstance basis so that for objects such as foliage where a singletriangle primitive represents a leaf, a ray is intersected with itregardless whether the triangle is back facing.

Although example embodiments were described with respect to a BVH as theacceleration structure and a ray as the query, embodiments are notlimited thereto. For example, in some other embodiments, the query maycomprise a beam or other geometric shape, rather than a ray, and/orhierarchical structures different from a BVH described above may be usedas the acceleration structure. A person of skill will also understandthat the specific mode flags, RayOp opcodes, ray parameter values, rvalparameters are examples, and that embodiments may include anycombination of those and/or other parameters to provide thequery-specific behavior modification of the traversal of an accelerationstructure.

The capabilities described above can be implemented in, or inassociation with, a parallel processing unit such as that describedbelow in relation to FIGS. 17-23.

More Detailed TTU and GPU Architecture

More illustrative information will now be set forth regarding variousoptional architectures and features with which the foregoing frameworkmay or may not be implemented, per the desires of the user. It should bestrongly noted that the following information is set forth forillustrative purposes and should not be construed as limiting in anymanner Any of the following features may be optionally incorporated withor without the exclusion of other features described.

Parallel Processing Architecture

FIG. 17 illustrates a parallel processing unit (PPU) 1700, in accordancewith an embodiment. In an embodiment, the PPU 1700 is a multi-threadedprocessor that is implemented on one or more integrated circuit devices.The PPU 1700 is a latency hiding architecture designed to process manythreads in parallel. A thread (i.e., a thread of execution) is aninstantiation of a set of instructions configured to be executed by thePPU 1700. In an embodiment, the PPU 1700 is a graphics processing unit(GPU, for example, such as that described in relation to FIG. 1)configured to implement a graphics rendering pipeline for processingthree-dimensional (3D) graphics data in order to generatetwo-dimensional (2D) image data for display on a display device such asa liquid crystal display (LCD) device. In other embodiments, the PPU1700 may be utilized for performing general-purpose computations. Whileone exemplary parallel processor is provided herein for illustrativepurposes, it should be strongly noted that such processor is set forthfor illustrative purposes only, and that any processor may be employedto supplement and/or substitute for the same.

One or more PPUs 1700 may be configured to accelerate thousands of HighPerformance Computing (HPC), data center, and machine learningapplications. The PPU 1700 may be configured to accelerate numerous deeplearning systems and applications including autonomous vehicleplatforms, deep learning, high-accuracy speech, image, and textrecognition systems, intelligent video analytics, molecular simulations,drug discovery, disease diagnosis, weather forecasting, big dataanalytics, astronomy, molecular dynamics simulation, financial modeling,robotics, factory automation, real-time language translation, onlinesearch optimizations, and personalized user recommendations, and thelike.

As shown in FIG. 17, the PPU 1700 includes an Input/Output (I/O) unit1705, a front end unit 1715, a scheduler unit 1720, a work distributionunit 1725, a hub 1730, a crossbar (Xbar) 1770, one or more generalprocessing clusters (GPCs) 1750, and one or more partition units 1780.The PPU 1700 may be connected to a host processor or other PPUs 1700 viaone or more high-speed NVLink 1710 interconnect. The PPU 1700 may beconnected to a host processor or other peripheral devices via aninterconnect 1702. The PPU 1700 may also be connected to a local memorycomprising a number of memory devices 1704. In an embodiment, the localmemory may comprise a number of dynamic random access memory (DRAM)devices. The DRAM devices may be configured as a high-bandwidth memory(HBM) subsystem, with multiple DRAM dies stacked within each device.

The NVLink 1710 interconnect enables systems to scale and include one ormore PPUs 1700 combined with one or more CPUs, supports cache coherencebetween the PPUs 1700 and CPUs, and CPU mastering. Data and/or commandsmay be transmitted by the NVLink 1710 through the hub 1730 to/from otherunits of the PPU 1700 such as one or more copy engines, a video encoder,a video decoder, a power management unit, etc. (not explicitly shown).The NVLink 1710 is described in more detail in conjunction with FIG. 22.

The I/O unit 1705 is configured to transmit and receive communications(i.e., commands, data, etc.) from a host processor (not shown) over theinterconnect 1702. The I/O unit 1705 may communicate with the hostprocessor directly via the interconnect 1702 or through one or moreintermediate devices such as a memory bridge. In an embodiment, the I/Ounit 1705 may communicate with one or more other processors, such as oneor more of the PPUs 1700 via the interconnect 1702. In an embodiment,the I/O unit 1705 implements a Peripheral Component Interconnect Express(PCIe) interface for communications over a PCIe bus and the interconnect1702 is a PCIe bus. In alternative embodiments, the I/O unit 1705 mayimplement other types of well-known interfaces for communicating withexternal devices.

The I/O unit 1705 decodes packets received via the interconnect 1702. Inan embodiment, the packets represent commands configured to cause thePPU 1700 to perform various operations. The I/O unit 1705 transmits thedecoded commands to various other units of the PPU 1700 as the commandsmay specify. For example, some commands may be transmitted to the frontend unit 1715. Other commands may be transmitted to the hub 1730 orother units of the PPU 1700 such as one or more copy engines, a videoencoder, a video decoder, a power management unit, etc. (not explicitlyshown). In other words, the I/O unit 1705 is configured to routecommunications between and among the various logical units of the PPU1700.

In an embodiment, a program executed by the host processor encodes acommand stream in a buffer that provides workloads to the PPU 1700 forprocessing. A workload may comprise several instructions and data to beprocessed by those instructions. The buffer is a region in a memory thatis accessible (i.e., read/write) by both the host processor and the PPU1700. For example, the I/O unit 1705 may be configured to access thebuffer in a system memory connected to the interconnect 1702 via memoryrequests transmitted over the interconnect 1702. In an embodiment, thehost processor writes the command stream to the buffer and thentransmits a pointer to the start of the command stream to the PPU 1700.The front end unit 1715 receives pointers to one or more commandstreams. The front end unit 1715 manages the one or more streams,reading commands from the streams and forwarding commands to the variousunits of the PPU 1700.

The front end unit 1715 is coupled to a scheduler unit 1720 thatconfigures the various GPCs 1750 to process tasks defined by the one ormore streams. The scheduler unit 1720 is configured to track stateinformation related to the various tasks managed by the scheduler unit1720. The state may indicate which GPC 1750 a task is assigned to,whether the task is active or inactive, a priority level associated withthe task, and so forth. The scheduler unit 1720 manages the execution ofa plurality of tasks on the one or more GPCs 1750.

The scheduler unit 1720 is coupled to a work distribution unit 1725 thatis configured to dispatch tasks for execution on the GPCs 1750. The workdistribution unit 1725 may track a number of scheduled tasks receivedfrom the scheduler unit 1720. In an embodiment, the work distributionunit 1725 manages a pending task pool and an active task pool for eachof the GPCs 1750. The pending task pool may comprise a number of slots(e.g., 32 slots) that contain tasks assigned to be processed by aparticular GPC 1750. The active task pool may comprise a number of slots(e.g., 4 slots) for tasks that are actively being processed by the GPCs1750. As a GPC 1750 finishes the execution of a task, that task isevicted from the active task pool for the GPC 1750 and one of the othertasks from the pending task pool is selected and scheduled for executionon the GPC 1750. If an active task has been idle on the GPC 1750, suchas while waiting for a data dependency to be resolved, then the activetask may be evicted from the GPC 1750 and returned to the pending taskpool while another task in the pending task pool is selected andscheduled for execution on the GPC 1750.

The work distribution unit 1725 communicates with the one or more GPCs1750 via XBar 1770. The XBar 1770 is an interconnect network thatcouples many of the units of the PPU 1700 to other units of the PPU1700. For example, the XBar 1770 may be configured to couple the workdistribution unit 1725 to a particular GPC 1750. Although not shownexplicitly, one or more other units of the PPU 1700 may also beconnected to the XBar 1770 via the hub 1730.

The tasks are managed by the scheduler unit 1720 and dispatched to a GPC1750 by the work distribution unit 1725. The GPC 1750 is configured toprocess the task and generate results. The results may be consumed byother tasks within the GPC 1750, routed to a different GPC 1750 via theXBar 1770, or stored in the memory 1704. The results can be written tothe memory 1704 via the partition units 1780, which implement a memoryinterface for reading and writing data to/from the memory 1704. Theresults can be transmitted to another PPU 1704 or CPU via the NVLink1710. In an embodiment, the PPU 1700 includes a number U of partitionunits 1780 that is equal to the number of separate and distinct memorydevices 1704 coupled to the PPU 1700. A partition unit 1780 will bedescribed in more detail below in conjunction with FIG. 18.

In an embodiment, a host processor executes a driver kernel thatimplements an application programming interface (API) that enables oneor more applications executing on the host processor to scheduleoperations for execution on the PPU 1700. In an embodiment, multiplecompute applications are simultaneously executed by the PPU 1700 and thePPU 1700 provides isolation, quality of service (QoS), and independentaddress spaces for the multiple compute applications. An application maygenerate instructions (i.e., API calls) that cause the driver kernel togenerate one or more tasks for execution by the PPU 1700. The driverkernel outputs tasks to one or more streams being processed by the PPU1700. Each task may comprise one or more groups of related threads,referred to herein as a warp. In an embodiment, a warp comprises 32related threads that may be executed in parallel. Cooperating threadsmay refer to a plurality of threads including instructions to performthe task and that may exchange data through shared memory. Threads andcooperating threads are described in more detail in conjunction withFIG. 20.

FIG. 19 illustrates a GPC 1750 of the PPU 1700 of FIG. 17, in accordancewith an embodiment. As shown in FIG. 19, each GPC 1750 includes a numberof hardware units for processing tasks. In an embodiment, each GPC 1750includes a pipeline manager 1810, a pre-raster operations unit (PROP)1815, a raster engine 1825, a work distribution crossbar (WDX) 1880, amemory management unit (MMU) 1890, and one or more Data ProcessingClusters (DPCs) 1820. It will be appreciated that the GPC 1750 of FIG.19 may include other hardware units in lieu of or in addition to theunits shown in FIG. 19.

In an embodiment, the operation of the GPC 1750 is controlled by thepipeline manager 1810. The pipeline manager 1810 manages theconfiguration of the one or more DPCs 1820 for processing tasksallocated to the GPC 1750. In an embodiment, the pipeline manager 1810may configure at least one of the one or more DPCs 1820 to implement atleast a portion of a graphics rendering pipeline. For example, a DPC1820 may be configured to execute a vertex shader program on theprogrammable streaming multiprocessor (SM) 1840. The pipeline manager1810 may also be configured to route packets received from the workdistribution unit 1725 to the appropriate logical units within the GPC1750. For example, some packets may be routed to fixed function hardwareunits in the PROP 1815 and/or raster engine 1825 while other packets maybe routed to the DPCs 1820 for processing by the primitive engine 1835or the SM 1840. In an embodiment, the pipeline manager 1810 mayconfigure at least one of the one or more DPCs 1820 to implement aneural network model and/or a computing pipeline.

The PROP unit 1815 is configured to route data generated by the rasterengine 1825 and the DPCs 1820 to a Raster Operations (ROP) unit,described in more detail in conjunction with FIG. 18. The PROP unit 1815may also be configured to perform optimizations for color blending,organize pixel data, perform address translations, and the like.

The raster engine 1825 includes a number of fixed function hardwareunits configured to perform various raster operations. In an embodiment,the raster engine 1825 includes a setup engine, a coarse raster engine,a culling engine, a clipping engine, a fine raster engine, and a tilecoalescing engine. The setup engine receives transformed vertices andgenerates plane equations associated with the geometric primitivedefined by the vertices. The plane equations are transmitted to thecoarse raster engine to generate coverage information (e.g., an x,ycoverage mask for a tile) for the primitive. The output of the coarseraster engine is transmitted to the culling engine where fragmentsassociated with the primitive that fail a z-test are culled, andnon-culled fragments are transmitted to a clipping engine wherefragments lying outside a viewing frustum are clipped. Those fragmentsthat survive clipping and culling may be passed to the fine rasterengine to generate attributes for the pixel fragments based on the planeequations generated by the setup engine. The output of the raster engine1825 comprises fragments to be processed, for example, by a fragmentshader implemented within a DPC 1820.

Each DPC 1820 included in the GPC 1750 includes an M-Pipe Controller(MPC) 1830, a primitive engine 1835, one or more SMs 1840, one or moreTexture Units 1842, and one or more TTU 1844. The TTU 1844 may operatesimilarly to TTU 700 described above. The MPC 1830 controls theoperation of the DPC 1820, routing packets received from the pipelinemanager 1810 to the appropriate units in the DPC 1820. For example,packets associated with a vertex may be routed to the primitive engine1835, which is configured to fetch vertex attributes associated with thevertex from the memory 1704. In contrast, packets associated with ashader program may be transmitted to the SM 1840.

The SM 1840 comprises a programmable streaming processor that isconfigured to process tasks represented by a number of threads. Each SM1840 is multi-threaded and configured to execute a plurality of threads(e.g., 32 threads) from a particular group of threads concurrently. Inan embodiment, the SM 1840 implements a SIMD (Single-Instruction,Multiple-Data) architecture where each thread in a group of threads(i.e., a warp) is configured to process a different set of data based onthe same set of instructions. All threads in the group of threadsexecute the same instructions. In another embodiment, the SM 1840implements a SIMT (Single-Instruction, Multiple Thread) architecturewhere each thread in a group of threads is configured to process adifferent set of data based on the same set of instructions, but whereindividual threads in the group of threads are allowed to diverge duringexecution. In an embodiment, a program counter, call stack, andexecution state is maintained for each warp, enabling concurrencybetween warps and serial execution within warps when threads within thewarp diverge. In another embodiment, a program counter, call stack, andexecution state is maintained for each individual thread, enabling equalconcurrency between all threads, within and between warps. Whenexecution state is maintained for each individual thread, threadsexecuting the same instructions may be converged and executed inparallel for maximum efficiency. The SM 1840 will be described in moredetail below in conjunction with FIGS. 20 and 21.

The MMU 1890 provides an interface between the GPC 1750 and thepartition unit 1780. The MMU 1890 may provide translation of virtualaddresses into physical addresses, memory protection, and arbitration ofmemory requests. In an embodiment, the MMU 1890 provides one or moretranslation lookaside buffers (TLBs) for performing translation ofvirtual addresses into physical addresses in the memory 1704.

FIG. 18 illustrates a memory partition unit 1780 of the PPU 1700 of FIG.17, in accordance with an embodiment. As shown in FIG. 18, the memorypartition unit 1780 includes a Raster Operations (ROP) unit 1850, alevel two (L2) cache 1860, and a memory interface 1870. The memoryinterface 1870 is coupled to the memory 1704. Memory interface 1870 mayimplement 32, 64, 128, 1024-bit data buses, or the like, for high-speeddata transfer. In an embodiment, the PPU 1700 incorporates U memoryinterfaces 1870, one memory interface 1870 per pair of partition units1780, where each pair of partition units 1780 is connected to acorresponding memory device 1704. For example, PPU 1700 may be connectedto up to Y memory devices 1704, such as high bandwidth memory stacks orgraphics double-data-rate, version 5, synchronous dynamic random accessmemory, or other types of persistent storage.

In an embodiment, the memory interface 1870 implements an HBM2 memoryinterface and Y equals half U. In an embodiment, the HBM2 memory stacksare located on the same physical package as the PPU 1700, providingsubstantial power and area savings compared with conventional GDDR5SDRAM systems. In an embodiment, each HBM2 stack includes four memorydies and Y equals 4, with HBM2 stack including two 128-bit channels perdie for a total of 8 channels and a data bus width of 1024 bits.

In an embodiment, the memory 1704 supports Single-Error CorrectingDouble-Error Detecting (SECDED) Error Correction Code (ECC) to protectdata. ECC provides higher reliability for compute applications that aresensitive to data corruption. Reliability is especially important inlarge-scale cluster computing environments where PPUs 1700 process verylarge datasets and/or run applications for extended periods.

In an embodiment, the PPU 1700 implements a multi-level memoryhierarchy. In an embodiment, the memory partition unit 1780 supports aunified memory to provide a single unified virtual address space for CPUand PPU 1700 memory, enabling data sharing between virtual memorysystems. In an embodiment the frequency of accesses by a PPU 1700 tomemory located on other processors is traced to ensure that memory pagesare moved to the physical memory of the PPU 1700 that is accessing thepages more frequently. In an embodiment, the NVLink 1710 supportsaddress translation services allowing the PPU 1700 to directly access aCPU's page tables and providing full access to CPU memory by the PPU1700.

In an embodiment, copy engines transfer data between multiple PPUs 1700or between PPUs 1700 and CPUs. The copy engines can generate page faultsfor addresses that are not mapped into the page tables. The memorypartition unit 1780 can then service the page faults, mapping theaddresses into the page table, after which the copy engine can performthe transfer. In a conventional system, memory is pinned (i.e.,non-pageable) for multiple copy engine operations between multipleprocessors, substantially reducing the available memory. With hardwarepage faulting, addresses can be passed to the copy engines withoutworrying if the memory pages are resident, and the copy process istransparent.

Data from the memory 1704 or other system memory may be fetched by thememory partition unit 1780 and stored in the L2 cache 1860, which islocated on-chip and is shared between the various GPCs 1750. As shown,each memory partition unit 1780 includes a portion of the L2 cache 1860associated with a corresponding memory device 1704. Lower level cachesmay then be implemented in various units within the GPCs 1750. Forexample, each of the SMs 1840 may implement a level one (L1) cache. TheL1 cache is private memory that is dedicated to a particular SM 1840.Data from the L2 cache 1860 may be fetched and stored in each of the L1caches for processing in the functional units of the SMs 1840. The L2cache 1860 is coupled to the memory interface 1870 and the XBar 1770.

The ROP unit 1850 performs graphics raster operations related to pixelcolor, such as color compression, pixel blending, and the like. The ROPunit 1850 also implements depth testing in conjunction with the rasterengine 1825, receiving a depth for a sample location associated with apixel fragment from the culling engine of the raster engine 1825. Thedepth is tested against a corresponding depth in a depth buffer for asample location associated with the fragment. If the fragment passes thedepth test for the sample location, then the ROP unit 1850 updates thedepth buffer and transmits a result of the depth test to the rasterengine 1825. It will be appreciated that the number of partition units1780 may be different than the number of GPCs 1750 and, therefore, eachROP unit 1850 may be coupled to each of the GPCs 1750. The ROP unit 1850tracks packets received from the different GPCs 1750 and determineswhich GPC 1750 that a result generated by the ROP unit 1850 is routed tothrough the Xbar 1770. Although the ROP unit 1850 is included within thememory partition unit 1780 in FIG. 18, in other embodiment, the ROP unit1850 may be outside of the memory partition unit 1780. For example, theROP unit 1850 may reside in the GPC 1750 or another unit.

Example Streaming Multiprocessor

The SM 1840 comprises a programmable streaming processor that isconfigured to process tasks represented by a number of threads. Each SM1840 is multi-threaded and configured to execute a plurality of threads(e.g., 32 threads comprising a warp) from a particular group of threadsconcurrently. In an embodiment, the SM 1840 implements a SIMD(Single-Instruction, Multiple-Data) architecture where each thread in agroup of threads (i.e., a warp) is configured to process a different setof data based on the same set of instructions. All threads in the groupof threads execute the same instructions. In another embodiment, the SM1840 implements a SIMT (Single-Instruction, Multiple Thread)architecture where each thread in a group of threads is configured toprocess a different set of data based on the same set of instructions,but where individual threads in the group of threads are allowed todiverge during execution. In an embodiment, a program counter, callstack, and execution state is maintained for each warp, enablingconcurrency between warps and serial execution within warps when threadswithin the warp diverge. In another embodiment, a program counter, callstack, and execution state is maintained for each individual thread,enabling equal concurrency between all threads, within and betweenwarps. When execution state is maintained for each individual thread,threads executing the same instructions may be converged and executed inparallel for maximum efficiency.

FIG. 20 illustrates the streaming multi-processor 1840 of FIG. 19, inaccordance with an embodiment. As shown in FIG. 20, the SM 1840 includesan instruction cache 1905, one or more scheduler units 1910, a registerfile 1920, one or more processing cores 1950, one or more specialfunction units (SFUs) 1952, one or more load/store units (LSUs) 1954, aninterconnect network 1980, a shared memory/L1 cache 1970.

As described above, the work distribution unit 1725 dispatches tasks forexecution on the GPCs 1750 of the PPU 1700. The tasks are allocated to aparticular DPC 1820 within a GPC 1750 and, if the task is associatedwith a shader program, the task may be allocated to an SM 1840. Thescheduler unit 1910 receives the tasks from the work distribution unit1725 and manages instruction scheduling for one or more thread blocksassigned to the SM 1840. The scheduler unit 1910 schedules thread blocksfor execution as warps of parallel threads, where each thread block isallocated at least one warp. In an embodiment, each warp executes 32threads. The scheduler unit 1910 may manage a plurality of differentthread blocks, allocating the warps to the different thread blocks andthen dispatching instructions from the plurality of differentcooperative groups to the various functional units (i.e., cores 1950,SFUs 1952, and LSUs 1954) during each clock cycle.

Cooperative Groups is a programming model for organizing groups ofcommunicating threads that allows developers to express the granularityat which threads are communicating, enabling the expression of richer,more efficient parallel decompositions. Cooperative launch APIs supportsynchronization amongst thread blocks for the execution of parallelalgorithms. Conventional programming models provide a single, simpleconstruct for synchronizing cooperating threads: a barrier across allthreads of a thread block (i.e., the syncthreads( ) function). However,programmers would often like to define groups of threads at smaller thanthread block granularities and synchronize within the defined groups toenable greater performance, design flexibility, and software reuse inthe form of collective group-wide function interfaces.

Cooperative Groups enables programmers to define groups of threadsexplicitly at sub-block (i.e., as small as a single thread) andmulti-block granularities, and to perform collective operations such assynchronization on the threads in a cooperative group. The programmingmodel supports clean composition across software boundaries, so thatlibraries and utility functions can synchronize safely within theirlocal context without having to make assumptions about convergence.Cooperative Groups primitives enable new patterns of cooperativeparallelism, including producer-consumer parallelism, opportunisticparallelism, and global synchronization across an entire grid of threadblocks.

A dispatch unit 1915 is configured to transmit instructions to one ormore of the functional units. In the embodiment, the scheduler unit 1910includes two dispatch units 1915 that enable two different instructionsfrom the same warp to be dispatched during each clock cycle. Inalternative embodiments, each scheduler unit 1910 may include a singledispatch unit 1915 or additional dispatch units 1915.

Each SM 1840 includes a register file 1920 that provides a set ofregisters for the functional units of the SM 1840. In an embodiment, theregister file 1920 is divided between each of the functional units suchthat each functional unit is allocated a dedicated portion of theregister file 1920. In another embodiment, the register file 1920 isdivided between the different warps being executed by the SM 1840. Theregister file 1920 provides temporary storage for operands connected tothe data paths of the functional units. FIG. 21 illustrates an exampleconfiguration of the registers files in the SM 1840.

Each SM 1840 comprises L processing cores 1950. In an embodiment, the SM1840 includes a large number (e.g., 128, etc.) of distinct processingcores 1950. Each core 1950 may include a fully-pipelined,single-precision, double-precision, and/or mixed precision processingunit that includes a floating point arithmetic logic unit and an integerarithmetic logic unit. In an embodiment, the floating point arithmeticlogic units implement the IEEE 754-2008 standard for floating pointarithmetic. In an embodiment, the cores 1950 include 64 single-precision(32-bit) floating point cores, 64 integer cores, 32 double-precision(64-bit) floating point cores, and 8 tensor cores.

Tensor cores are configured to perform matrix operations, and, in anembodiment, one or more tensor cores are included in the cores 1950. Inparticular, the tensor cores are configured to perform deep learningmatrix arithmetic, such as convolution operations for neural networktraining and inferencing. In an embodiment, each tensor core operates ona 4×4 matrix and performs a matrix multiply and accumulate operationD=A><B+C, where A, B, C, and D are 4×4 matrices.

In an embodiment, the matrix multiply inputs A and B are 16-bit floatingpoint matrices, while the accumulation matrices C and D may be 16-bitfloating point or 32-bit floating point matrices. Tensor Cores operateon 16-bit floating point input data with 32-bit floating pointaccumulation. The 16-bit floating point multiply requires 64 operationsand results in a full precision product that is then accumulated using32-bit floating point addition with the other intermediate products fora 4×4×4 matrix multiply. In practice, Tensor Cores are used to performmuch larger two-dimensional or higher dimensional matrix operations,built up from these smaller elements. An API, such as CUDA 9 C++ API,exposes specialized matrix load, matrix multiply and accumulate, andmatrix store operations to efficiently use Tensor Cores from a CUDA-C++program. At the CUDA level, the warp-level interface assumes 16×16 sizematrices spanning all 32 threads of the warp.

Each SM 1840 also comprises M SFUs 1952 that perform special functions(e.g., attribute evaluation, reciprocal square root, and the like). Inan embodiment, the SFUs 1952 may include a tree traversal unitconfigured to traverse a hierarchical tree data structure. In anembodiment, the SFUs 1952 may include texture unit configured to performtexture map filtering operations. In an embodiment, the texture unitsare configured to load texture maps (e.g., a 2D array of texels) fromthe memory 1704 and sample the texture maps to produce sampled texturevalues for use in shader programs executed by the SM 1840. In anembodiment, the texture maps are stored in the shared memory/L1 cache1970. The texture units implement texture operations such as filteringoperations using mip-maps (i.e., texture maps of varying levels ofdetail). In an embodiment, each SM 1740 includes two texture units.

Each SM 1840 also comprises N LSUs 1954 that implement load and storeoperations between the shared memory/L1 cache 1970 and the register file1920. Each SM 1840 includes an interconnect network 1980 that connectseach of the functional units to the register file 1920 and the LSU 1954to the register file 1920, shared memory/L1 cache 1970. In anembodiment, the interconnect network 1980 is a crossbar that can beconfigured to connect any of the functional units to any of theregisters in the register file 1920 and connect the LSUs 1954 to theregister file and memory locations in shared memory/L1 cache 1970.

The shared memory/L1 cache 1970 is an array of on-chip memory thatallows for data storage and communication between the SM 1840 and theprimitive engine 1835 and between threads in the SM 1840. In anembodiment, the shared memory/L1 cache 1970 comprises 128 KB of storagecapacity and is in the path from the SM 1840 to the partition unit 1780.The shared memory/L1 cache 1970 can be used to cache reads and writes.One or more of the shared memory/L1 cache 1970, L2 cache 1860, andmemory 1704 are backing stores.

Combining data cache and shared memory functionality into a singlememory block provides the best overall performance for both types ofmemory accesses. The capacity is usable as a cache by programs that donot use shared memory. For example, if shared memory is configured touse half of the capacity, texture and load/store operations can use theremaining capacity. Integration within the shared memory/L1 cache 1970enables the shared memory/L1 cache 1970 to function as a high-throughputconduit for streaming data while simultaneously providing high-bandwidthand low-latency access to frequently reused data.

FIG. 21 illustrates one example architecture for the SM 1840. Asillustrated in FIG. 19, the SM 1840 may be coupled to one or moreTexture Unit 1842 and/or one or more TTUs 700. As a compromise betweenperformance and area, one example non-limiting embodiment may include asingle Texture Unit 1842 and/or a single TTU 700 per groups of SMs 1840(e.g., See FIG. 19). The TTU 700 may communicate with the SMs 1840 via aTTU input/output block in memory input-output and with a L1 cache via adedicated read interface. In one example embodiment, the TTU 700 onlyreads from the main memory and does not write to the main memory.

Example More Detailed TTU Architecture

As discussed above, the TTU 700 may be a coprocessor to the SM 1840.Like a texture processor, it is exposed via a set of SM instructions,accesses memory as a read-only client of the L1 cache, and returnsresults into the SM register file. Unlike some texture processors, theamount of data that may need to be passed into and out of the TTU 700for a typical query makes it difficult in some embodiments to specifyall the source and destination registers in a single instruction (andbecause most of this data is unique per-thread, there is no TTU analogueof texture headers and samplers). As a consequence, the TTU 700 in someembodiments is programmed via a multi-instruction sequence. Thissequence can be conceptualized as a single “macro-instruction” in someimplementations.

Also like a Texture Units 1842, the TTU 700 in some implementations mayrely on certain read-only data structures in memory that areprepopulated by software. These include:

One or more BVHs, where each BVH is for example a tree of axis-alignedbounding boxes, stored in a compressed format that greatly reducesmemory traffic compared to an uncompressed representation. Each node inthe BVH is stored as a complet structure, with size and alignment insome implementations matched to that of an L1 cache line. Child completsof a given parent are preferably stored contiguously in memory and childpointers are stored in compressed form.

Zero or more instance nodes, which provide a way to connect a leaf ofone BVH to the root of another. An instance node may be a data structurethat is also aligned. This structure may contain a pointer to thesub-BVH, flags that affect back-face culling behavior in the sub-BVH,and a matrix that corresponds to the first three rows of an arbitrarytransformation matrix (in homogeneous coordinates) from the coordinatesystem of the top-level BVH (commonly “world space”) to that of thesub-BVH (commonly “object space”). The final row of the matrix in someembodiments is in some implementations implicitly (0, 0, 0, 1).

Zero or more triangle or other primitive buffers, containing for exampletriangles stored either as a triplet of coordinates per vertex or in alossless compressed format understood by the TTU 700. In addition, analpha bit may be provided per triangle or other primitive, indicatingtriangles that require special handling by software to determine whetherthe triangle is actually intersected by a given ray. Triangle bufferscan be organized into blocks. There may also be a per-triangleforce-no-cull function bit. When set, that bit indicates that both sidesof the triangle should be treated as front-facing or back-facing withrespect to culling, i.e., the triangle should not be culled because theray intersects the “back” instead of the “front”. The simplest use casefor this is a single triangle used to represent a leaf, where we canstill see the leaf if the ray hits it on the back surface.

The TTU 700 in some embodiments is stateless, meaning that noarchitectural state is maintained in the TTU between queries. At thesame time, it is often useful for software running on the SM 1840 torequest continuation of a previous query, which implies that relevantstate should be written to registers by the TTU 700 and then passed backto the TTU in registers (often in-place) to continue. This state maytake the form of a traversal stack that tracks progress in the traversalof the BVH.

A small number of stack initializers may also be provided for beginninga new query of a given type, for example:

-   -   Traversal starting from a complet    -   Intersection of a ray with a range of triangles    -   Intersection of a ray with a range of triangles, followed by        traversal starting from a complet    -   Vertex fetch from a triangle buffer for a given triangle    -   Optional support for instance transforms in front of the        “traversal starting from a complet” and “intersection of a ray        with a range of triangles”.

Vertex fetch is a simple query that may be specified with request datathat consists of a stack initializer and nothing else. Other query typesmay require the specification of a ray or beam, along with the stack orstack initializer and various ray flags describing details of the query.A ray is given by its three-coordinate origin, three-coordinatedirection, and minimum and maximum values for the t-parameter along theray. A beam is additionally given by a second origin and direction.

Various ray flags can be used to control various aspects of traversalbehavior, back-face culling, and handling of the various child nodetypes, subject to a pass/fail status of an optional rayOp test. RayOpsadd considerable flexibility to the capabilities of the TTU. In someexample embodiments, the RayOps portion introduces two Ray Flag versionscan be dynamically selected based on a specified operation on dataconveyed with the ray and data stored in the complet. To explore suchflags, it's first helpful to understand the different types of childnodes allowed within a BVH, as well as the various hit types that theTTU 700 can return to the SM. Example node types are:

-   -   A child complet (i.e., an internal node)        By default, the TTU 700 continues traversal by descending into        child complets.    -   A triangle range, corresponding to a contiguous set of triangles        within a triangle buffer    -   (1) By default, triangle ranges encountered by a ray are handled        natively by the TTU 700 by testing the triangles for        intersection and shortening the ray accordingly. If traversal        completes and a triangle was hit, default behavior is for the        triangle ID to be returned to SM 1840, along with the t-value        and barycentric coordinates of the intersection. This is the        “Triangle” hit type.    -   (2) By default, intersected triangles with the alpha bit set are        returned to SM 1840 even if traversal has not completed. The        returned traversal stack contains the state required to continue        traversal if software determines that the triangle was in fact        transparent.    -   (3) Triangle intersection in some embodiments is not supported        for beams, so encountered triangle ranges are by default        returned to SM 1840 as a “TriRange” hit type, which includes a        pointer to the first triangle block overlapping the range,        parameters specifying the range, and the t-value of the        intersection with the leaf bounding box.    -   An item range, consisting of an index (derived from a        user-provided “item range base” stored in the complet) and a        count of items.

By default, item ranges are returned to SM 1840 as an “ItemRange” hittype, consisting of for example an index, a count, and the t-value ofthe intersection with the leaf bounding box.

-   -   An instance node.

The TTU 700 in some embodiments can handle one level of instancingnatively by transforming the ray into the coordinate system of theinstance BVH. Additional levels of instancing (or every other level ofinstancing, depending on strategy) may be handled in software. The“InstanceNode” hit type is provided for this purpose, consisting of apointer to the instance node and the tvalue of the intersection with theleaf bounding box. In other implementations, the hardware can handletwo, three or more levels of instancing.

In addition to the node-specific hit types, a generic “NodeRef” hit typeis provided that consists of a pointer to the parent complet itself, aswell as an ID indicating which child was intersected and the t-value ofthe intersection with the bounding box of that child.

An “Error” hit type may be provided for cases where the query or BVH wasimproperly formed or if traversal encountered issues during traversal.

A “None” hit type may be provided for the case where the ray or beammisses all geometry in the scene.

How the TTU handles each of the four possible node types is determinedby a set of node-specific mode flags set as part of the query for agiven ray. The “default” behavior mentioned above corresponds to thecase where the mode flags are set to all zeros.

Alternative values for the flags allow for culling all nodes of a giventype, returning nodes of a given type to SM as a NodeRef hit type, orreturning triangle ranges or instance nodes to SM using theircorresponding hit types, rather than processing them natively within theTTU 700.

Additional mode flags may be provided for control handling of alphatriangles.

When configured for general purpose parallel computation, a simplerconfiguration can be used compared with graphics processing.Specifically, the fixed function graphics processing units shown in FIG.17, are bypassed, creating a much simpler programming model. In thegeneral purpose parallel computation configuration, the workdistribution unit 1725 assigns and distributes blocks of threadsdirectly to the DPCs 1820. The threads in a block execute the sameprogram, using a unique thread ID in the calculation to ensure eachthread generates unique results, using the SM 1840 to execute theprogram and perform calculations, shared memory/L1 cache 1970 tocommunicate between threads, and the LSU 1954 to read and write globalmemory through the shared memory/L1 cache 1970 and the memory partitionunit 1780. When configured for general purpose parallel computation, theSM 1840 can also write commands that the scheduler unit 1720 can use tolaunch new work on the DPCs 1820. The TTU 700 can be used to acceleratespatial queries in the context of general purpose computation.

The PPU 1700 may be included in a desktop computer, a laptop computer, atablet computer, servers, supercomputers, a smart-phone (e.g., awireless, hand-held device), personal digital assistant (PDA), a digitalcamera, a vehicle, a head mounted display, a hand-held electronicdevice, and the like. In an embodiment, the PPU 1700 is embodied on asingle semiconductor substrate. In another embodiment, the PPU 1700 isincluded in a system-on-a-chip (SoC) along with one or more otherdevices such as additional PPUs 1700, the memory 204, a reducedinstruction set computer (RISC) CPU, a memory management unit (MMU), adigital-to-analog converter (DAC), and the like.

In an embodiment, the PPU 1700 may be included on a graphics card thatincludes one or more memory devices 1704. The graphics card may beconfigured to interface with a PCIe slot on a motherboard of a desktopcomputer. In yet another embodiment, the PPU 1700 may be an integratedgraphics processing unit (iGPU) or parallel processor included in thechipset of the motherboard.

Exemplary Computing System

Systems with multiple GPUs and CPUs are used in a variety of industriesas developers expose and leverage more parallelism in applications suchas artificial intelligence computing. High-performance GPU-acceleratedsystems with tens to many thousands of compute nodes are deployed indata centers, research facilities, and supercomputers to solve everlarger problems. As the number of processing devices within thehigh-performance systems increases, the communication and data transfermechanisms need to scale to support the increased data transmissionbetween the processing devices.

FIG. 22 is a conceptual diagram of a processing system 1900 implementedusing the PPU 1700 of FIG. 17, in accordance with an embodiment. Theexemplary system 1900 may be configured to implement one or more methodsdisclosed in this application. The processing system 1900 includes a CPU1930, switch 1912, and multiple PPUs 1700 each and respective memories1704. The NVLink 1710 provides high-speed communication links betweeneach of the PPUs 1700. Although a particular number of NVLink 1710 andinterconnect 1702 connections are illustrated in FIG. 22, the number ofconnections to each PPU 1700 and the CPU 1930 may vary. The switch 1912interfaces between the interconnect 1702 and the CPU 1930. The PPUs1700, memories 1704, and NVLinks 1710 may be situated on a singlesemiconductor platform to form a parallel processing module 1925. In anembodiment, the switch 1912 supports two or more protocols to interfacebetween various different connections and/or links.

In another embodiment (not shown), the NVLink 1710 provides one or morehigh-speed communication links between each of the PPUs 1700 and the CPU1930 and the switch 1912 interfaces between the interconnect 1702 andeach of the PPUs 1700. The PPUs 1700, memories 1704, and interconnect1702 may be situated on a single semiconductor platform to form aparallel processing module 1925. In yet another embodiment (not shown),the interconnect 1702 provides one or more communication links betweeneach of the PPUs 1700 and the CPU 1930 and the switch 1912 interfacesbetween each of the PPUs 1700 using the NVLink 1710 to provide one ormore high-speed communication links between the PPUs 1700. In anotherembodiment (not shown), the NVLink 1710 provides one or more high-speedcommunication links between the PPUs 1700 and the CPU 1930 through theswitch 1912. In yet another embodiment (not shown), the interconnect1702 provides one or more communication links between each of the PPUs1700 directly. One or more of the NVLink 1710 high-speed communicationlinks may be implemented as a physical NVLink interconnect or either anon-chip or on-die interconnect using the same protocol as the NVLink1710.

In the context of the present description, a single semiconductorplatform may refer to a sole unitary semiconductor-based integratedcircuit fabricated on a die or chip. It should be noted that the termsingle semiconductor platform may also refer to multi-chip modules withincreased connectivity which simulate on-chip operation and makesubstantial improvements over utilizing a conventional busimplementation. Of course, the various circuits or devices may also besituated separately or in various combinations of semiconductorplatforms per the desires of the user. Alternately, the parallelprocessing module 1925 may be implemented as a circuit board substrateand each of the PPUs 1700 and/or memories 1704 may be packaged devices.In an embodiment, the CPU 1930, switch 1912, and the parallel processingmodule 1925 are situated on a single semiconductor platform.

In an embodiment, the signaling rate of each NVLink 1710 is 20 to 25Gigabits/second and each PPU 1700 includes six NVLink 1710 interfaces(as shown in FIG. 22, five NVLink 1710 interfaces are included for eachPPU 1700). Each NVLink 1710 provides a data transfer rate of 25Gigabytes/second in each direction, with six links providing 1700Gigabytes/second. The NVLinks 1710 can be used exclusively forPPU-to-PPU communication as shown in FIG. 22, or some combination ofPPU-to-PPU and PPU-to-CPU, when the CPU 1930 also includes one or moreNVLink 1710 interfaces.

In an embodiment, the NVLink 1710 allows direct load/store/atomic accessfrom the CPU 1930 to each PPU's 1700 memory 1704. In an embodiment, theNVLink 1710 supports coherency operations, allowing data read from thememories 1704 to be stored in the cache hierarchy of the CPU 1930,reducing cache access latency for the CPU 1930. In an embodiment, theNVLink 1710 includes support for Address Translation Services (ATS),allowing the PPU 1700 to directly access page tables within the CPU1930. One or more of the NVLinks 1710 may also be configured to operatein a low-power mode.

FIG. 23 illustrates an exemplary system 1965 in which the variousarchitecture and/or functionality of the various previous embodimentsmay be implemented. The exemplary system 1965 may be configured toimplement one or more methods disclosed in this application.

As shown, a system 1965 is provided including at least one centralprocessing unit 1930 that is connected to a communication bus 1975. Thecommunication bus 1975 may be implemented using any suitable protocol,such as PCI (Peripheral Component Interconnect), PCI-Express, AGP(Accelerated Graphics Port), HyperTransport, or any other bus orpoint-to-point communication protocol(s). The system 1965 also includesa main memory 1940. Control logic (software) and data are stored in themain memory 1940 which may take the form of random access memory (RAM).

The system 1965 also includes input devices 1960, the parallelprocessing system 1925, and display devices 1945, i.e. a conventionalCRT (cathode ray tube), LCD (liquid crystal display), LED (lightemitting diode), plasma display or the like. User input may be receivedfrom the input devices 1960, e.g., keyboard, mouse, touchpad,microphone, and the like. Each of the foregoing modules and/or devicesmay even be situated on a single semiconductor platform to form thesystem 1965. Alternately, the various modules may also be situatedseparately or in various combinations of semiconductor platforms per thedesires of the user.

Further, the system 1965 may be coupled to a network (e.g., atelecommunications network, local area network (LAN), wireless network,wide area network (WAN) such as the Internet, peer-to-peer network,cable network, or the like) through a network interface 1935 forcommunication purposes.

The system 1965 may also include a secondary storage (not shown). Thesecondary storage includes, for example, a hard disk drive and/or aremovable storage drive, representing a floppy disk drive, a magnetictape drive, a compact disk drive, digital versatile disk (DVD) drive,recording device, universal serial bus (USB) flash memory. The removablestorage drive reads from and/or writes to a removable storage unit in awell-known manner

Computer programs, or computer control logic algorithms, may be storedin the main memory 1940 and/or the secondary storage. Such computerprograms, when executed, enable the system 1965 to perform variousfunctions. The memory 1940, the storage, and/or any other storage arepossible examples of computer-readable media.

The architecture and/or functionality of the various previous figuresmay be implemented in the context of a general computer system, acircuit board system, a game console system dedicated for entertainmentpurposes, an application-specific system, and/or any other desiredsystem. For example, the system 1965 may take the form of a desktopcomputer, a laptop computer, a tablet computer, servers, supercomputers,a smart-phone (e.g., a wireless, hand-held device), personal digitalassistant (PDA), a digital camera, a vehicle, a head mounted display, ahand-held electronic device, a mobile phone device, a television,workstation, game consoles, embedded system, and/or any other type oflogic.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

Graphics Processing Pipeline

In an embodiment, the PPU 1700 comprises a graphics processing unit(GPU). The PPU 1700 is configured to receive commands that specifyshader programs for processing graphics data. Graphics data may bedefined as a set of primitives such as points, lines, triangles, quads,triangle strips, and the like. Typically, a primitive includes data thatspecifies a number of vertices for the primitive (e.g., in a model-spacecoordinate system) as well as attributes associated with each vertex ofthe primitive. The PPU 1700 can be configured to process the graphicsprimitives to generate a frame buffer (i.e., pixel data for each of thepixels of the display).

An application writes model data for a scene (i.e., a collection ofvertices and attributes) to a memory such as a system memory or memory1704. The model data defines each of the objects that may be visible ona display. The application then makes an API call to the driver kernelthat requests the model data to be rendered and displayed. The driverkernel reads the model data and writes commands to the one or morestreams to perform operations to process the model data. The commandsmay reference different shader programs to be implemented on the SMs1840 of the PPU 1700 including one or more of a vertex shader, hullshader, domain shader, geometry shader, a pixel shader, a ray generationshader, a ray intersection shader, a ray hit shader, and a ray missshader (these correspond to the shaders defined by the DXR API, ignoringany distinction between “closest-hit” and “any-hit” shaders; seehttps://devblogs.nvidia.com/introduction-nvidia-rtx-directx-ray-tracing/).For example, one or more of the SMs 1840 may be configured to execute avertex shader program that processes a number of vertices defined by themodel data. In an embodiment, the different SMs 1840 may be configuredto execute different shader programs concurrently. For example, a firstsubset of SMs 1840 may be configured to execute a vertex shader programwhile a second subset of SMs 1840 may be configured to execute a pixelshader program. The first subset of SMs 1840 processes vertex data toproduce processed vertex data and writes the processed vertex data tothe L2 cache 1860 and/or the memory 1704. After the processed vertexdata is rasterized (i.e., transformed from three-dimensional data intotwo-dimensional data in screen space) to produce fragment data, thesecond subset of SMs 1840 executes a pixel shader to produce processedfragment data, which is then blended with other processed fragment dataand written to the frame buffer in memory 1704. The vertex shaderprogram and pixel shader program may execute concurrently, processingdifferent data from the same scene in a pipelined fashion until all ofthe model data for the scene has been rendered to the frame buffer.Then, the contents of the frame buffer are transmitted to a displaycontroller for display on a display device.

FIG. 24 is a conceptual diagram of a graphics processing pipeline 2000implemented by the PPU 1700 of FIG. 17, in accordance with anembodiment. The graphics processing pipeline 2000 is an abstract flowdiagram of the processing steps implemented to generate 2Dcomputer-generated images from 3D geometry data. As is well-known,pipeline architectures may perform long latency operations moreefficiently by splitting up the operation into a plurality of stages,where the output of each stage is coupled to the input of the nextsuccessive stage. Thus, the graphics processing pipeline 2000 receivesinput data 2001 that is transmitted from one stage to the next stage ofthe graphics processing pipeline 2000 to generate output data 2002. Inan embodiment, the graphics processing pipeline 2000 may represent agraphics processing pipeline defined by the OpenGL® API. As an option,the graphics processing pipeline 2000 may be implemented in the contextof the functionality and architecture of the previous Figures.

As shown in FIG. 24, the graphics processing pipeline 2000 comprises apipeline architecture that includes a number of stages. The stagesinclude, but are not limited to, a data assembly stage 2010, a vertexshading stage 2020, a primitive assembly stage 2030, a geometry shadingstage 2040, a viewport scale, cull, and clip (VSCC) stage 2050, arasterization stage 2060, a fragment shading stage 2070, and a rasteroperations stage 2080. In an embodiment, the input data 2001 comprisescommands that configure the processing units to implement the stages ofthe graphics processing pipeline 2000 and geometric primitives (e.g.,points, lines, triangles, quads, triangle strips or fans, etc.) to beprocessed by the stages. The output data 2002 may comprise pixel data(i.e., color data) that is copied into a frame buffer or other type ofsurface data structure in a memory.

The data assembly stage 2010 receives the input data 2001 that specifiesvertex data for high-order surfaces, primitives, or the like. The dataassembly stage 2010 collects the vertex data in a temporary storage orqueue, such as by receiving a command from the host processor thatincludes a pointer to a buffer in memory and reading the vertex datafrom the buffer. The vertex data is then transmitted to the vertexshading stage 2020 for processing.

The vertex shading stage 2020 processes vertex data by performing a setof operations (i.e., a vertex shader or a program) once for each of thevertices. Vertices may be, e.g., specified as a 4-coordinate vector(i.e., <x, y, z, w>) associated with one or more vertex attributes(e.g., color, texture coordinates, surface normal, etc.). The vertexshading stage 2020 may manipulate individual vertex attributes such asposition, color, texture coordinates, and the like. In other words, thevertex shading stage 2020 performs operations on the vertex coordinatesor other vertex attributes associated with a vertex. Such operationscommonly including lighting operations (i.e., modifying color attributesfor a vertex) and transformation operations (i.e., modifying thecoordinate space for a vertex). For example, vertices may be specifiedusing coordinates in an object-coordinate space, which are transformedby multiplying the coordinates by a matrix that translates thecoordinates from the object-coordinate space into a world space or anormalized-device-coordinate (NCD) space. The vertex shading stage 2020generates transformed vertex data that is transmitted to the primitiveassembly stage 2030.

The primitive assembly stage 2030 collects vertices output by the vertexshading stage 2020 and groups the vertices into geometric primitives forprocessing by the geometry shading stage 2040. For example, theprimitive assembly stage 2030 may be configured to group every threeconsecutive vertices as a geometric primitive (i.e., a triangle) fortransmission to the geometry shading stage 2040. In some embodiments,specific vertices may be reused for consecutive geometric primitives(e.g., two consecutive triangles in a triangle strip may share twovertices). The primitive assembly stage 2030 transmits geometricprimitives (i.e., a collection of associated vertices) to the geometryshading stage 2040.

The geometry shading stage 2040 processes geometric primitives byperforming a set of operations (i.e., a geometry shader or program) onthe geometric primitives. Tessellation operations may generate one ormore geometric primitives from each geometric primitive. In other words,the geometry shading stage 2040 may subdivide each geometric primitiveinto a finer mesh of two or more geometric primitives for processing bythe rest of the graphics processing pipeline 2000. The geometry shadingstage 2040 transmits geometric primitives to the viewport SCC stage2050.

In an embodiment, the graphics processing pipeline 2000 may operatewithin a streaming multiprocessor and the vertex shading stage 2020, theprimitive assembly stage 2030, the geometry shading stage 2040, thefragment shading stage 2070, and/or hardware/software associatedtherewith, may sequentially perform processing operations. Once thesequential processing operations are complete, in an embodiment, theviewport SCC stage 2050 may utilize the data. In an embodiment,primitive data processed by one or more of the stages in the graphicsprocessing pipeline 2000 may be written to a cache (e.g. L1 cache, avertex cache, etc.). In this case, in an embodiment, the viewport SCCstage 2050 may access the data in the cache. In an embodiment, theviewport SCC stage 2050 and the rasterization stage 2060 are implementedas fixed function circuitry.

The viewport SCC stage 2050 performs viewport scaling, culling, andclipping of the geometric primitives. Each surface being rendered to isassociated with an abstract camera position. The camera positionrepresents a location of a viewer looking at the scene and defines aviewing frustum that encloses the objects of the scene. The viewingfrustum may include a viewing plane, a rear plane, and four clippingplanes. Any geometric primitive entirely outside of the viewing frustummay be culled (i.e., discarded) because the geometric primitive will notcontribute to the final rendered scene. Any geometric primitive that ispartially inside the viewing frustum and partially outside the viewingfrustum may be clipped (i.e., transformed into a new geometric primitivethat is enclosed within the viewing frustum. Furthermore, geometricprimitives may each be scaled based on a depth of the viewing frustum.All potentially visible geometric primitives are then transmitted to therasterization stage 2060.

The rasterization stage 2060 converts the 3D geometric primitives into2D fragments (e.g. capable of being utilized for display, etc.). Therasterization stage 2060 may be configured to utilize the vertices ofthe geometric primitives to setup a set of plane equations from whichvarious attributes can be interpolated. The rasterization stage 2060 mayalso compute a coverage mask for a plurality of pixels that indicateswhether one or more sample locations for the pixel intercept thegeometric primitive. In an embodiment, z-testing may also be performedto determine if the geometric primitive is occluded by other geometricprimitives that have already been rasterized. The rasterization stage2060 generates fragment data (i.e., interpolated vertex attributesassociated with a particular sample location for each covered pixel)that are transmitted to the fragment shading stage 2070.

The fragment shading stage 2070 processes fragment data by performing aset of operations (i.e., a fragment shader or a program) on each of thefragments. The fragment shading stage 2070 may generate pixel data(i.e., color values) for the fragment such as by performing lightingoperations or sampling texture maps using interpolated texturecoordinates for the fragment. The fragment shading stage 2070 generatespixel data that is transmitted to the raster operations stage 2080.

The raster operations stage 2080 may perform various operations on thepixel data such as performing alpha tests, stencil tests, and blendingthe pixel data with other pixel data corresponding to other fragmentsassociated with the pixel. When the raster operations stage 2080 hasfinished processing the pixel data (i.e., the output data 2002), thepixel data may be written to a render target such as a frame buffer, acolor buffer, or the like.

It will be appreciated that one or more additional stages may beincluded in the graphics processing pipeline 2000 in addition to or inlieu of one or more of the stages described above. Variousimplementations of the abstract graphics processing pipeline mayimplement different stages. Furthermore, one or more of the stagesdescribed above may be excluded from the graphics processing pipeline insome embodiments (such as the geometry shading stage 2040). Other typesof graphics processing pipelines are contemplated as being within thescope of the present disclosure. Furthermore, any of the stages of thegraphics processing pipeline 2000 may be implemented by one or morededicated hardware units within a graphics processor such as PPU 200.Other stages of the graphics processing pipeline 2000 may be implementedby programmable hardware units such as the SM 1840 of the PPU 1700.

The graphics processing pipeline 2000 may be implemented via anapplication executed by a host processor, such as a CPU. In anembodiment, a device driver may implement an application programminginterface (API) that defines various functions that can be utilized byan application in order to generate graphical data for display. Thedevice driver is a software program that includes a plurality ofinstructions that control the operation of the PPU 1700. The APIprovides an abstraction for a programmer that lets a programmer utilizespecialized graphics hardware, such as the PPU 1700, to generate thegraphical data without requiring the programmer to utilize the specificinstruction set for the PPU 1700. The application may include an APIcall that is routed to the device driver for the PPU 1700. The devicedriver interprets the API call and performs various operations torespond to the API call. In some instances, the device driver mayperform operations by executing instructions on the CPU. In otherinstances, the device driver may perform operations, at least in part,by launching operations on the PPU 1700 utilizing an input/outputinterface between the CPU and the PPU 1700. In an embodiment, the devicedriver is configured to implement the graphics processing pipeline 2000utilizing the hardware of the PPU 1700.

Various programs may be executed within the PPU 1700 in order toimplement the various stages of the graphics processing pipeline 2000.For example, the device driver may launch a kernel on the PPU 1700 toperform the vertex shading stage 2020 on one SM 1840 (or multiple SMs1840). The device driver (or the initial kernel executed by the PPU1800) may also launch other kernels on the PPU 1800 to perform otherstages of the graphics processing pipeline 2000, such as the geometryshading stage 2040 and the fragment shading stage 2070. In addition,some of the stages of the graphics processing pipeline 2000 may beimplemented on fixed unit hardware such as a rasterizer or a dataassembler implemented within the PPU 1800. It will be appreciated thatresults from one kernel may be processed by one or more interveningfixed function hardware units before being processed by a subsequentkernel on an SM 1840.

Machine Learning

Deep neural networks (DNNs) developed on processors, such as the PPU1700 have been used for diverse use cases, from self-driving cars tofaster drug development, from automatic image captioning in online imagedatabases to smart real-time language translation in video chatapplications. Deep learning is a technique that models the neurallearning process of the human brain, continually learning, continuallygetting smarter, and delivering more accurate results more quickly overtime. A child is initially taught by an adult to correctly identify andclassify various shapes, eventually being able to identify shapeswithout any coaching Similarly, a deep learning or neural learningsystem needs to be trained in object recognition and classification forit get smarter and more efficient at identifying basic objects, occludedobjects, etc., while also assigning context to objects.

At the simplest level, neurons in the human brain look at various inputsthat are received, importance levels are assigned to each of theseinputs, and output is passed on to other neurons to act upon. Anartificial neuron or perceptron is the most basic model of a neuralnetwork. In one example, a perceptron may receive one or more inputsthat represent various features of an object that the perceptron isbeing trained to recognize and classify, and each of these features isassigned a certain weight based on the importance of that feature indefining the shape of an object.

A deep neural network (DNN) model includes multiple layers of manyconnected perceptrons (e.g., nodes) that can be trained with enormousamounts of input data to quickly solve complex problems with highaccuracy. In one example, a first layer of the DLL model breaks down aninput image of an automobile into various sections and looks for basicpatterns such as lines and angles. The second layer assembles the linesto look for higher level patterns such as wheels, windshields, andmirrors. The next layer identifies the type of vehicle, and the finalfew layers generate a label for the input image, identifying the modelof a specific automobile brand.

Once the DNN is trained, the DNN can be deployed and used to identifyand classify objects or patterns in a process known as inference.Examples of inference (the process through which a DNN extracts usefulinformation from a given input) include identifying handwritten numberson checks deposited into ATM machines, identifying images of friends inphotos, delivering movie recommendations to over fifty million users,identifying and classifying different types of automobiles, pedestrians,and road hazards in driverless cars, or translating human speech inreal-time.

During training, data flows through the DNN in a forward propagationphase until a prediction is produced that indicates a labelcorresponding to the input. If the neural network does not correctlylabel the input, then errors between the correct label and the predictedlabel are analyzed, and the weights are adjusted for each feature duringa backward propagation phase until the DNN correctly labels the inputand other inputs in a training dataset. Training complex neural networksrequires massive amounts of parallel computing performance, includingfloating-point multiplications and additions that are supported by thePPU 1700. Inferencing is less compute-intensive than training, being alatency-sensitive process where a trained neural network is applied tonew inputs it has not seen before to classify images, translate speech,and generally infer new information.

Neural networks rely heavily on matrix math operations, and complexmulti-layered networks require tremendous amounts of floating-pointperformance and bandwidth for both efficiency and speed. With thousandsof processing cores, optimized for matrix math operations, anddelivering tens to hundreds of TFLOPS of performance, the PPU 1700 is acomputing platform capable of delivering performance required for deepneural network-based artificial intelligence and machine learningapplications.

While the invention has been described in connection with what ispresently considered to be the most practical and preferred embodiments,it is to be understood that the invention is not to be limited to thedisclosed embodiments, but on the contrary, is intended to cover variousmodifications and equivalent arrangements included within the spirit andscope of the appended claims.

What is claimed is:
 1. A method of ray tracing, comprising: accessingray data corresponding to a ray and an acceleration data structurecorresponding to a scene; traversing the acceleration data structure inaccordance with the ray data; during the traversing, performing for atleast one node in the acceleration data structure an intersection testbased upon geometric attributes of the ray and the acceleration datastructure and an auxiliary ray operation test; based on results of theintersection test and the auxiliary ray operation test, during thetraversing, performing at least one of changing a state of thetraversing and selecting an output data corresponding to one or morenodes of the acceleration data structure intersected by the ray; andproviding output data from the traversing to a rendering process forrendering at least a portion of the scene to a display.
 2. The methodaccording to claim 1, wherein the performing an intersection test and anauxiliary ray operation test comprises selecting the ray operation testbased upon an opcode in the ray data.
 3. The method according to claim2, wherein the performing an intersection test and an auxiliary rayoperation test further comprises performing the selected ray operationtest based upon at least one parameter each from the ray data and the atleast one node.
 4. The method according to claim 3, wherein the at leastone parameter from the ray data is configurable per ray and the at leastone parameter from the at least one node is configurable per node. 5.The method according to claim 3, wherein the performing an intersectiontest and an auxiliary ray operation test further comprises performingthe selected ray operation test based on non-geometric attributes of theray and the acceleration data structure.
 6. The method according toclaim 2, wherein the performing an intersection test and an auxiliaryray operation test further comprises performing the selected rayoperation test based upon one parameter from the at least one node andthe opcode.
 7. The method according to claim 2, wherein the performingat least one of changing a state of the traversing and selecting anoutput data comprises choosing said at least one of changing a state ofthe traversing and selecting an output data based at least on one ormore mode flags specified in the ray data.
 8. The method according toclaim 7, wherein said one or more mode flags are selected based on anode type of the at least one node.
 9. The method according to claim 8,wherein said one or more mode flags are selected based further on aresult of the auxiliary ray operation test.
 10. The method according toclaim 7, wherein the perform at least one of changing a state of thetraversing and selecting an output data further comprises changing,based on said one or more mode flags, an order in which respective nodesin the accelerated data structure are traversed during said traversing.11. The method according to claim 7, wherein the perform at least one ofchanging a state of the traversing and selecting an output data furthercomprises dynamically changing, based on said one or more mode flags, astructure of the accelerated data structure by culling a portion of theaccelerated data structure.
 12. The method according to claim 7, whereinthe choosing said at least one of changing a state of the traversing andselecting an output data based on one or more mode flags specified inthe ray data further comprises choosing in accordance with one or moreoverride flags in the at least one node.
 13. The method according toclaim 12, wherein the at least one node is an instance node.
 14. Themethod according to claim 12, wherein the at least one node represents aprimitive and at least one of the override flags is configured tooverride a culling configuration specified in the ray data.
 15. Themethod according to claim 2, wherein the performing for at least onenode in the acceleration data structure an intersection test based upongeometric attributes associated with the ray and geometric attributesassociated with the acceleration data structure and an auxiliary rayoperation test comprises performing the auxiliary ray operation testbased on said opcode, wherein said opcode provides for comparing a valuecomputed during the intersection test scaled by one geometric attributeassociated with the ray and biased by another geometric attributeassociated with the ray to at least one geometric parameter associatedwith the at least one node.
 16. The method according to claim 2, whereinthe performing for at least one node in the acceleration data structurean intersection test based upon geometric attributes of the ray and theacceleration data structure and an auxiliary ray operation testcomprises performing the auxiliary ray operation test based on saidopcode, wherein said opcode provides for comparing a distance associatedwith the ray to at least one parameter of the at least one node.
 17. Themethod according to claim 2, wherein the performing for at least onenode in the acceleration data structure an intersection test based upongeometric attributes of the ray and the acceleration data structure andan auxiliary ray operation test comprises performing the auxiliary rayoperation test based on said opcode, wherein said opcode provides forcomparing a first value based on at least one parameter in the ray datato a second value based on at least one parameter of the at least onenode.
 18. The method according to claim 2, wherein the performing for atleast one node in the acceleration data structure an intersection testbased upon geometric attributes of the ray and the acceleration datastructure and an auxiliary ray operation test comprises performing theauxiliary ray operation test based on said opcode, wherein said opcodeprovides for comparing a size of a surface area represented in the atleast one node based upon at least one parameter from the at least onenode with a distance along the ray at which an intersection occurs. 19.The method according to claim 1, further comprising rendering, by aparallel processor, the scene to the display based at least in part onthe output data provided by a traversal processor executing saidtraversing.
 20. A system comprising a traversal coprocessor comprisinghardware processing circuitry for traversing acceleration datastructures, configured to: access ray data corresponding to a ray and anacceleration data structure corresponding to a scene; traverse theacceleration data structure in accordance with the ray data; during thetraversing, perform for at least one node in the acceleration datastructure an intersection test based upon geometric attributes of theray and the acceleration data structure and an auxiliary ray operationtest; based on results of the intersection test and the auxiliary rayoperation test, during the traversing, perform at least one of changinga state of the traversing and selecting an output data corresponding toone or more nodes of the acceleration data structure intersected by theray; and provide output data from the traversing to a rendering processfor rendering at least a portion of the scene to a display.
 21. Thesystem according to claim 20, further comprising a parallel processorconfigured to generate said ray data corresponding to the ray and theacceleration data structure corresponding to a model of the scene. 22.The system according to claim 21, wherein the ray data includes one ormore ray parameters, one or more opcodes and one or more mode flags,wherein the at least one node includes at least one node parameter, andwherein the system is further configured to: perform said auxiliary rayoperation test by comparing, based upon at least one of the opcodes,values derived from the one or more ray parameters and the at least onenode parameter; select one or more of said mode flags based at leastupon a result of the auxiliary test; and perform said at least one ofchanging a state of the traversing and selecting an output datacorresponding to one or more nodes of the acceleration data structureintersected by the ray based on the selected one or more said modeflags.
 23. A coprocessor for accelerating traversal of a tree datastructure, comprising: interface circuitry configured to communicatewith a multiprocessor and a memory to receive a plurality of query datastructures, the tree data structure, and a query command, wherein eachquery data structure includes query test parameters, a test opcode andmode flags, and wherein a node in the tree data structure includes anode test parameter; and tree traversal circuitry configured to: inresponse to the query command, traverse the tree data structure inaccordance with each of the query data structures; and determine foreach of the query data structures: a result of tests based upon theopcode and the query test parameters of the respective query datastructures and the node test parameter of the node in the tree datastructure; and changing the traversing or one or more outputs returnedbased upon the result and the mode flags of the respective query datastructures.